Building for Operability: Stateful Applications in Containers with the Autopilot Pattern - Philly ETE 2017

Building for Operability: Stateful Applications in Containers with the Autopilot Pattern - Philly ETE 2017

ChariotSolutions via YouTube Direct link

Initialization

21 of 22

21 of 22

Initialization

Class Central Classrooms beta

YouTube playlists 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. 1 Intro
  2. 2 Why stateful containers?
  3. 3 Immutable: deploy a versioned artifact
  4. 4 Minimal overhead: ship only* the application
  5. 5 A container is the unit of deployment.
  6. 6 A group of containers is the unit of deployment (ex. K8s pods, Swarm stack, Triton deployment )
  7. 7 A container can't persist data.
  8. 8 Problem: Service Discovery
  9. 9 Problem: Load Balancing
  10. 10 Problem: Automated Fail-over
  11. 11 Host volumes solve the problem of persistence in containers.
  12. 12 orchestrator and
  13. 13 3 requirements
  14. 14 Ability to provision containers across multiple compute nodes
  15. 15 Network virtualization (ex. VXLan)
  16. 16 IP inside the container
  17. 17 Infrastructure-backed discovery bootstrap
  18. 18 We might need some help
  19. 19 habitat
  20. 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. 21 Initialization
  22. 22 Empower development teams to operationalize their applications

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.