Guest: Julian Fischer (LinkedIn)
Company: anynines
Show Name: KubeStruck
Topic: Kubernetes

The rise of Kubernetes has led many to believe it’s a one-size-fits-all solution for application delivery. But Julian Fischer, CEO & Founder of anynines, offers a reality check: Kubernetes was never built to be a developer platform.

“Throwing developers in front of Vanilla Kubernetes is potentially not a good idea at scale,” Fischer said. “It doesn’t deliver the kind of application developer experience that a developer platform would.”

For Fischer, that’s where Cloud Foundry continues to play a critical role. The classic Cloud Foundry stack, while VM-based, still provides a streamlined developer experience that abstracts away complexity—making it ideal for organizations with thousands of developers.

But Cloud Foundry doesn’t need to compete with Kubernetes. Tools like Korifi, which brings the Cloud Foundry experience to Kubernetes, enable hybrid strategies. “We’ve seen clients asking for Cloud Foundry developer experience in more remote regions or smaller setups—without rolling out a full VM-based stack,” Fischer noted.

The lighter footprint of Korifi opens the door to smaller organizations that may not have massive monthly infrastructure budgets but still require a polished DevEx layer.

Looking ahead, Fischer anticipates fragmentation in the Kubernetes ecosystem. “Within the next 24 months, a lot of application delivery stacks will pop up… with different opinionation and different assumptions,” he said. “There will never be this one technology again that dominates it all.”

That means we’re heading toward a more diversified application platform landscape. Cloud Foundry and Korifi will continue to serve opinionated use cases, while new stacks will emerge to serve others.

In this vision of the future, organizations can mix and match platform layers based on geography, budget, and team size—without compromising on the developer experience.