What comes after Kubernetes? | InfoWorld

“Boring.” That’s a person of the finest compliments you can spend an infrastructure technologies. No a person wishes to run their mission-vital programs on “spicy!” But uninteresting? Tedious is good.

Tedious suggests that a technologies has attained a specified amount of ubiquity and believe in, that it is properly-understood and conveniently managed. Kubernetes, in generation at seventy eight p.c of enterprises, has arguably handed that issue, obtaining develop into greatly acknowledged as standard cloud-enabling plumbing that “just works.”

Or, normally stated, has develop into “boring.”

Even as the Cloud Indigenous Computing Foundation aids coordinate the development of a variety of other initiatives to fill in any blanks left behind by Kubernetes at the infrastructure layer, the Kubernetes dialogue has commenced to shift to what is occurring higher up the stack. In April, developer advocate superstar Kelsey Hightower observed that Kubernetes only solves fifty percent the challenge in modernizing programs, if that:

There is a ton of effort and hard work making an attempt to “modernize” programs at the infrastructure layer, but without the need of equivalent expense at the software layer, assume frameworks and software servers, we’re only fixing fifty percent the challenge.

What do we do about this?

Filling the hole concerning apps and infrastructure

“There’s a big hole concerning the infrastructure and building a comprehensive software,” stated Jonas Bonér, CTO and co-founder at Lightbend, in an interview. Bonér served to get started the open up resource venture Akka, which is aimed at fixing a complex challenge established concerning the infrastructure and software, previously mentioned Kubernetes on the stack. As Bonér put it: 

Copyright © 2020 IDG Communications, Inc.