Habitat in Production
summary
Habitat’s Supervisor deploys and choreographs services with concrete behaviors: service topologies include standalone and leader-based clusters with a quorum of three before starting processes; bindings are required or optional (example: Rails package binds Postgres, Ruby scaffolding uses optional bind); update strategies are none, at-once, and a one-at-a-time rolling update with an update leader polling the Depot (~60s); release channels let teams promote the same immutable artifact; key types (origin, ring, service, user) secure packages and gossip; config can be env, file under /hab/svc/<pkg>, or config apply via gossip using an integer incarnation.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:32What is Habitat
- 2:41Agenda
- 3:07Topology
- 8:22Service Bindings
- 15:38Update Strategies
- 18:38Rolling Strategy
- 21:42Release Channels
- 26:13Keys
- 32:43Service Configuration
related talks
28mHabitat Automation that travels with the app
37mHabitat Essentials - An Absolute Beginner's Guide
39mSimplifying Container Operations with Habitat
39mAchieving Cloud Agnostic Application Deployment with Habitat
40mCan an Enterprise Run Habitat? Or Course!
45mThe Evolution Of Automation
05mIgnite: Introduction to Habitat
36mMeshing Legacy Systems with Habitat Deployed Components to...