Chef announces new solution for cloud native architectures
Chef is building on top of its application automation solution with the release of a new SaaS-based service. Habitat was first announced last year as a way to give apps the ability to self-organize and self-configure throughout their lifecycle. Today’s announcement of Habitat Builder adds to that technology by enabling modern application development teams to build, deploy, and manage cloud native applications.
With Habitat, teams can connect to their source code, package and build apps, deploy those apps in any format and runtime, and manage those apps in any cloud native architecture, according to the company. Chef explains it decided to tackle cloud native architectures in this release because of the industry’s move to the cloud, growth of containers, accessibility of containers in the cloud and the recent uptake in microservices.
“What happens in a cloud native architecture is you become more application-centric about how you think about application delivery,” said Marc Holmes, vice president of marketing for Chef. “That is what Habitat is seeking to do, which is how do you think about operations for application delivery against a cloud native backdrop?”
The solution features GitHub SCM and authentication integration, automated builds, automated dependency rebuilds, public and private origins, release channels for continuous delivery, container publishing to Docker Hub, scaffolding for Node.js and Ruby, and more than 500 packages for common applications and libraries.
Development teams can take advantage of the solution’s build service for consistent package and build services; its artifact store for deploying package artifacts to a desired architecture; and its application supervision for consistent management capabilities.
“While the application portability benefits of containers are widely recognized, lack of consistency in packaging and orchestration across the application lifecycle has, in many cases, limited the success of their deployment at scale, even when using cloud-native architectures,” said Stephen Elliot, program vice president at IDC. “Separating packaging, deployment concerns, and artifacts is one strategy that can empower teams to deliver on business objectives of delivering software at speed, with high quality.”
Deel dit nieuws op
JOUW BERICHT HIER?