First look: Chef’s Habitat puts automation in the app

By packaging configuration and runtime requirements with the app, Habitat decouples automation from the infrastructure

Become An Insider

Sign up now and get FREE access to hundreds of Insider articles, guides, reviews, interviews, blogs, and other premium content. Learn more.

Deploying new software to production can be hard -- really hard. If you’re among the many businesses adopting new infrastructure and deployment technology today, you’re keenly aware of how difficult it can be. Even as you adopt modern devops tools to streamline development, test, deployment, and ongoing management, and to bring development and operations teams closer together, it often seems you're only creating new silos.

The fundamental problem is that all of the information critical to each application’s lifecycle -- build dependencies, runtime dependencies, configuration settings -- remain scattered across separate tools devoted to separate stages of the application lifecycle. An open source project called Habitat, from the people who brought us Chef, promises a better way, one that cuts across all of these silos. 

To continue reading this article register now