Launching patterns for containers - it's more than just scheduling
summary
Argues that container scheduling must handle more than placement: it must support long‑running APIs, message consumers, scheduled batch jobs and safe rolling upgrades. Shows Docker images on Azure Container Service with Mesosphere DC/OS / Mesos, Marathon and Chronos, plus Kafka and Chronos for messaging and jobs. Uses a three‑node management pattern with ~5 agent nodes, highlights three-node minimum for Kafka brokers, demos consumers that flap safely and a job pattern that can queue 2,500 jobs while honoring resource requests like 0.2 CPU.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:02Container platforms
- 2:18Common commonalities
- 3:25Infrastructure
- 5:54Core features
- 9:28Scheduling
- 11:10Resource allocation
- 13:02Resource constraints
- 15:31More than is available
- 16:11Server density
- 18:00Longrunning tasks
- 22:53DCOs Cluster
- 26:59Grouping applications
- 27:29Deploying an API
- 29:38Deploying a task
- 40:26What is Kafka
- 42:58Flapping
- 44:38Debug
- 49:58Brute Force
- 50:48Events
- 52:28History
- 53:58Waiting
- 55:18Creating a new user
- 56:18Changing the environment variable
- 57:38Kafka example
related talks
37mContainer Service: Not Only
01h 18mEmbracing Docker simplicity - while harnessing platform power
53mDocker as the Building Block for Datacenter-Scale Applications
01h 06mSo many Docker platforms, so little time...
51mDeploying And Scaling Microservices
22mKeynote: Are We There Yet?
01h 07mDocker Containers on Azure - let me count the ways
48mContainer: check! Aber wohin mit Persistent Data, Big Data oder Fast Data?!
