Strict Application Definitions for Failure Free Deployments
Chef Habitat gives application teams complete control of every dependency running within their environment. Each dependency is defined and stored as an independent and reusable object. This ensures consistency and that you don’t have the lingering “drift” problem that is common in organizations scaling agile development practice, container deployments and/or running multiple operating systems.
Pre-Built Content and a Robust Open Source User Community to Jump Start Adoption
Chef Habitat is 100% open source and users have access to hundreds of pre-built plans to get up and running quickly. These include common application dependencies such as .NET, jdk or gcc, utilities like Maven, Gradle, or NuGet, and middleware like Tomcat, HAProxy, or Memcached. Additionally, Chef Habitat supports scaffolding for languages like Ruby, Go, and Node.JS to further ease the build and install process.
Clean Rooms for Clean Builds
The Chef Habitat Studio is a development kit for creating automated build and deployment plans for any application and then testing them in a clean-room environment. This enables application teams to “shift-left” more testing into the build state. The Habitat Studio creates a localized and isolated clean room that separates the build environment from all other tools and applications running on the user’s machine. If a requirement or dependency is missing the build will then fail on the user’s machine. This ensures what is built and run in development will be exactly the same in production and eliminates the age-old “worked fine on my machine” excuse.
Single Artifacts for Simpler Pipelines
Chef Habitat packages the Application Manifest into an immutable artifact called the Habitat Application Artifact (.HART) file. By bundling dependencies, lifecycle events, and compiled code into a single artifact, Habitat greatly simplifies CI/CD pipelines in any environment by providing a single means to build or promote an app regardless of its language or target platform. Chef Habitat simplifies channel management, supports roll-backs, roll-forwards and multiple deployment patterns (Canary, Blue/Green, All At Once, or Feature Flag).
Universal Application Packages for Multi-Modal Delivery
Habitat artifacts can be exported to run in a variety of runtimes with zero refactoring or rewriting. Available export formats include tarball, Docker, or directly to container registries (Azure Container Registry, Amazon Elastic Container Registry, or Docker Hub). This eliminates the need for DevOps teams to create separate versions of applications based on the runtime environment.
Trusted Application Deployments
Organizations must be able to not only deliver application updates quickly, but also validate that every instance of the application was successfully updated. The Chef Automate Application Dashboard tracks the status of applications holistically across all environments. With a click of the mouse, interested parties can see what applications have been updated, what the status is and where there are failures.