Coté

Coté

Cloud Foundry is alive and well, running lots of really important shit

Here’s my talk from Cloud Foundry Day. It’s four stories of large organizations using Cloud Foundry:

Three are banks, and one is a German tax accountant and back-office SaaS. I start talking about the value of case studies for enterprise software. The opening keynote was from the German police, the Bundeskriminalamt (BKA).

We used to have a lot of case studiess in the Cloud Foundry world and interest in PaaS in general, but that dropped off during The Great Kubernetes Distraction of the 2020’s.1 It’s time to bring those stories back because there are so many of them.

Cloud Foundry is used in really big organizations to run really important workloads. And, as the case studies go over, the efficiency numbers are astounding (a handful of operations people can support hundreds, sometimes thousands of applications), it’s stable, and developers have very good developers experience and the ability to deploy weekly, if not dealy.

In summary, everything you want to do with a “platform” can be done with Cloud Foundry. This is especially true for “private cloud.” What’s astonishing is that many large organizations already have Cloud Foundry installed, paid for, and available. The rest of those large organizations could get it setup pretty quickly. You can even try a 90 day trial of Cloud Foundry to test that claim out.

The industry is re-inventing PaaS and Cloud Foundry, wasting a lot of time and money again building a platform.

My theory is that AI app build outs will drive a new interest in application development - the type we saw in the digital transformation 2010’s. You see people like Anthropic figuring out PaaS like things with Claude Skills.2

AI, mostly chat apps, are a new type of user interface, and new interfaces usually drive loads of new applications, which drives new interest in platforms.

Cloud Foundry is perfect for that kind of platform. It’s built around the notion of speeding up the application lifecycle by standardizing ops, and removing developer toil.

Hopefully we in the Cloud Foundry community can get our marketing act together to get people interested in it again. I went over part one of my recommendations at the previous Cloud Foundry Day, and you can check out part two in the recent talk.

Relevant to your interests

Originally from the Bull and Mouth Inn, now hidden away at The Museum of London.

Wastebook

Logoff

No conferences for the rest of the year, just one trip.

Also, I should mention: we interviewed Manton on Software Defined Interviews. He’s a delight, and runs the service that runs my blog.

Using the draw cards Claude Skill with the GameMaster’s Apprentice deck.

Since they came out on Friday, I’ve been playing around with Claude Agent Skills.3 They are amazing for people like me: someone who can barely code and can do almost zero of the “toil” around applications.

That toil is basic things like knowing how to setup new projects, figure out runtimes like node and even Java - I’m baffled by how many steps it takes to just check in git files. And how do you arrange a TypeScript project? Spring Boot is great in this respect: it has strong opinions about all of that build time stuff and you truly do just spend time coding. I suspect Node/JavaScript and TypeScript are like that too: I just don’t know the conventions.

These skills are so easy, though. I’ll write more about them, but you can see two of my skills in this Bluesky thread, with links to the GitHb repos.

1

The Kubernetes thought-leaders frequently commented on Kubernetes not being a platform for many years: Kubernetes is a platform for building platforms; everyone wants a PaaS, they just insist on building it themselves; make sure you really need Kubernetes, because you probably don’t; and, we never intended for developers to see all that yaml. Despite that, the industry as a whole seems to have thought of Kubernetes like it was a PaaS.

2

You bundle up an application, with actual code, upload it to Claude which sticks it in a VM/container and runs it. That is exactly a PaaS, and how Cloud Foundry thinks of the world, just with buildpacks instead of a zip file with a SKILL.md file.

3

Or as Whitney realized one should phrase it “researching.”


@cote@cote.io, @cote@cote.io @cote, @cote.io https://proven.lol/a60da7,