

Information technology is going application centric, and it’s making developers heads of the house. They’re influencing procurement decisions in organizations and also how vendors engineer technology from the start — and not just dev tools.
With developers largely opting for containers that live fast and die young, how will that shape their offerings?
“The application developers are in control now,” said Mathew Ericson (pictured), senior product manager at Commvault Systems Inc. Commvault has assimilated this reality into its R&D and has asked developers to educate it on what works for them. What they’ve said is that they’re developing with containers and Kubernetes for agility.
“When they do that, they’re looking for solutions that match how they deploy their applications,” said David Ngo (pictured), vice president of Metallic products and engineering at Commvault. Supporting actors that won’t stall the show tend to come in software as-a-service packages, Ngo added.
Ericson and Ngo spoke with Joep Piscaer, guest host of theCUBE, SiliconANGLE Media’s livestreaming studio, during the KubeCon + CloudNativeCon NA event. They discussed the superiority of SaaS for modern development and what developer-led backup looks like for containerized apps in Kubernetes. (* Disclosure below.)
Metallic has engineered developer input into its backup and data-management SaaS for containers and Kubernetes. This means: “Basically take input from the developer on what information is important and needs to be protected and then protecting it,” Ericson said.
Luckily for Metallic, it’s fully cloud native and effectively integrates and speaks natively with the Kubernetes API Server. It therefore has a direct line to the system of truth — the Kubernetes orchestrator itself, Ericson explained. So, for example, a user can schedule a backup for every four hours, and it will step out and ask Kubernetes what apps exist within it. It then maps all of the API resources associated with applications, backs them up and, crucially, grabs the data from them as well.
“That allows us to then replay or schedule that application either back to that original cluster or to another one for application mobility with data,” Ericson said.
Application and data mobility sans time-consuming migration work are pillars of the agile-IT ideal.
“So it’s your easy button to keep Kubernetes development protected while you keep pace with the innovation within your organization,” Ericson concluded.
Watch the complete video interview below, and be sure to check out more of SiliconANGLE’s and theCUBE’s coverage of the KubeCon + CloudNativeCon NA event. (* Disclosure: Commvault Systems Inc. sponsored this segment of theCUBE. Neither Commvault nor other sponsors have editorial control over content on theCUBE or SiliconANGLE.)
THANK YOU