Completed
Problem: Automated Fail-over
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Building for Operability: Stateful Applications in Containers with the Autopilot Pattern - Philly ETE 2017
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 Why stateful containers?
- 3 Immutable: deploy a versioned artifact
- 4 Minimal overhead: ship only* the application
- 5 A container is the unit of deployment.
- 6 A group of containers is the unit of deployment (ex. K8s pods, Swarm stack, Triton deployment )
- 7 A container can't persist data.
- 8 Problem: Service Discovery
- 9 Problem: Load Balancing
- 10 Problem: Automated Fail-over
- 11 Host volumes solve the problem of persistence in containers.
- 12 orchestrator and
- 13 3 requirements
- 14 Ability to provision containers across multiple compute nodes
- 15 Network virtualization (ex. VXLan)
- 16 IP inside the container
- 17 Infrastructure-backed discovery bootstrap
- 18 We might need some help
- 19 habitat
- 20 Know your guarantees: Asynchronous replication Unavailable for writes during failover Possible stale reads during failover . May drop client-acknowledged writes during failover Consistent between nod…
- 21 Initialization
- 22 Empower development teams to operationalize their applications
