Diamanti’s mission is to help large enterprises both simplify and scale Kubernetes and container deployments across a wide range of on-premises and multi- and hybrid-cloud infrastructures.
The new additions to Diamanti’s platforms are expected to help engineers and developers address a number of headaches typically experienced when working on cloud native and Kubernetes platforms, such as “noisy neighbor” or “non-determinacy” issues, said Brian Waldon, vice president, product, for Diamanti.
“A lot of these problems occur in cloud or virtualized environments,” Waldon said. “So, from my perspective, the immediate benefit [of these releases] is really time savings.”
Diamanti seeks to provide consistency between traditional stateful applications and Kubernetes apps by extending data protection, performance, reliability and network auditing capabilities, Torsten Volk, an analyst for Enterprise Management Associates (EMA), said. “Achieving this consistency has proven tricky and therefore costly for many enterprises that now all of a sudden have to operate one part of their applications in the old world of servers, hypervisors and middleware and the other in the stateless, scalable and generally policy-driven world of Kubernetes,” Volk said.
Diamanti’s release thus underscores how platform providers are increasingly extending stateful applications, particularly for storage, into Kubernetes and cloud native infrastructures.
“While the first wave of container applications were mostly stateless web applications that did not require data persistence, a growing number of enterprises are now containerizing stateful applications that maintain application and system data.” Jay Lyman, principal analyst, cloud native and DevOps, 451 Research (now part of S&P Global Market Intelligence), told The New Stack.
Indeed, according to 451 Research’s recent “Voice of the Enterprise: DevOps” survey, for the first quarter of 2020, 56% of the 430 enterprise IT decision-makers and practitioners in North America reported more than half of their container applications are stateful. “Part of this has to do with organizations containerizing a broader set of applications that now include databases, data services and applications that use them,” Lyman said. “This also represents the maturation of Kubernetes and stateful services, such as persistent storage volumes, to support these stateful applications that are also distributed.”
With Kubernetes deployments, there is a need for “bread and butter enterprises capabilities,” especially for stateful applications, Volk said. These include backup and restore, snapshotting, data encryption and offsite replication, all of which “can become very tricky when force-fitting traditional applications onto the Kubernetes platform,” Volk said.
“Kubernetes was designed to manage immutable cloud native applications where individual microservices can be individually started, scaled, and updated without having to worry about preserving stateful information,” Volk said. “The pressure to move to Kubernetes quickly has forced many organizations to come up with their own stitched together solutions to handle stateful applications. The more custom elements are added, the more brittle the overall application becomes and the riskier the upgrade path.”
The need for improved Kubernetes infrastructure support for security for cloud native environments and storage, including disaster recovery capabilities, has created a vacuum for software makers, including, of course, Diamanti.
“While the Kubernetes storage SIG is working on better supporting these traditional enterprise storage capabilities, these will not become simple turnkey solutions,” Volk said. “But simplicity is exactly what enterprises want for their digital transformation process and every staff hour spent on worrying about backup, security and disaster recovery is no longer available for creating new app capabilities that will dazzle customers.”
Diamanti is a sponsor of The New Stack.
Feature image from Pixabay.