Cloud Foundry

Right, so the code for your applications, for your agents, for your workflows, it, of course, needs a place, needs a home or needs a place to run on.

And Business AI Platform actually gives you various runtime environments which serve different purposes, right? So the Cloud Foundry that many of our customers, many of our partners are familiar with is most widely used for the solutions, container-based, mature, well-supported for both traditional applications and agent workflows as well.

So most builders working with engines today are on Cloud Foundry.

It is a proven, well-paved path and the one I would recommend to most teams starting off now.

Then there are other options.

So that is a significant operational advantage for some customers and partners, especially for smaller teams that cannot afford a dedicated infrastructure functions.

Okay, great.

So we now spoke about, let's recap, Cloud Foundry, we spoke about Kuma, the ABAP environment, and the managed runtime, which you said is also going to come soon.

So you can plug in any platform which you want.

For example, you can imagine having support for Cloud Foundry applications in the future.

Okay, but if you say it's open for, that would mean there is a bit of work to do until it handles, for instance, Cloud Foundry-based applications or something completely different.

Yes.

Okay, okay.

Hey, everyone.

Welcome to Cloud Foundry Weekly.

I'm Nick Kuhn.

Each week, we explore Cloud Foundry, Tanzu, and what's next for developers from platform engineering to AI with hands-on demos and conversations from across the community.

Now, let's jump into the episode.

Yeah.

Yeah.

So

That's what it's become.

Now, you go back to Cloud Foundry, and it was not that, right? It was trying to be...

an opinionated platform that the developer had intent and then the platform could enforce or deploy that intent.

But that's not where we ended up with things like Kubernetes.

I mean, linguistically, it ties to cybernetics because Kubernetes introduced this idea of a reconciliation loop as a vocabulary term.

Cloud Foundry and other systems of the time may have had similar concepts baked in, but Kubernetes gave us the phrase reconciliation loop.

And that's where you have set what you want to be true.

You want three instances of this thing and you are setting an intention.

So, I mean, you've done two summits over the course of the last, what, three weeks? Yes.

You did Midwest AI Summit yesterday, and then you also were in Germany for Cloud Foundry Summit back, I think it was, what, at the end of September.

Yes.

So talk a little bit about just, like, your observations, your experiences.

CF.

Which no one, no one asked the Cloud Foundry people if they could, uh, you know, borrow it, but that's fine.

You know, they, they should, they should borrow it for a-

Well, I was gonna ask you-

... great command line tool

... someone put in there.

I assume there was at some point a command line utility named CF in Cloud Foundry or, or no?

There, there, yeah, there, there still is.

I don't remember his exact title, but, but I will say kind of the senior technical architect.

It was Cloud Foundry.

Yeah.

Right.

They bought, um, uh, uh, did the, the certified container images of various software.

I can't think of the-- I wanna say Bit Foundry, but that's not right.

Um, and kind of brought it together into this new modern app, right? So they took the Cloud Foundry from Pivotal, um, the, the data pieces from Pivotal, and, um, then you've got Heptio, right? This is as the, as Kubernetes is just taking off, and how could they kind of bring this together, right? Cloud Foundry was and, and frankly is awesome.

Um, you know, that, that platform as a service.