What comes after Kubernetes? | InfoWorld

“Boring.” That’s one of the best compliments you can pay an infrastructure technology. No one wants to run their mission-critical applications on “spicy!” But boring? Boring is good.

Boring means that a technology has reached a certain level of ubiquity and trust, that it’s well-understood and easily managed. Kubernetes, in production at 78 percent of enterprises, has arguably passed that point, having become widely recognized as standard cloud-enabling plumbing that “just works.”

Or, otherwise said, has become “boring.”

Even as the Cloud Native Computing Foundation helps coordinate the development of a range of other projects to fill in any blanks left behind by Kubernetes at the infrastructure layer, the Kubernetes conversation has started to shift to what’s happening higher up the stack. In April, developer advocate superstar Kelsey Hightower observed that Kubernetes only solves half the problem in modernizing applications, if that:

There’s a ton of effort attempting to “modernize” applications at the infrastructure layer, but without equal investment at the application layer, think frameworks and application servers, we’re only solving half the problem.

What do we do about this?

Filling the gap between apps and infrastructure

“There’s a huge gap between the infrastructure and building a full application,” said Jonas Bonér, CTO and co-founder at Lightbend, in an interview. Bonér helped to start the open source project Akka, which is aimed at solving a complex problem set between the infrastructure and application, above Kubernetes on the stack. As Bonér put it: 

Copyright © 2020 IDG Communications, Inc.



Source link