Deploying And Scaling Microservices

on YouTube ↗51m

" summary

Argues that independent deployability and one artifact for all environments are the rules, and shows tradeoffs between Docker Swarm, Mesos+Marathon and Kubernetes: Docker images become the practical artifact; AMI builds take 15–20 minutes; Mesos runs mixed workloads and underpins large systems (Siri cited at ~30,000 nodes) via frameworks; Swarm historically lacked desired‑state rebalance; Kubernetes uses pods and kubelets but had scaling hiccups around 100 nodes. Recommends baking off platforms against these realities.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 10:52What do we want from an artifact?
3. 11:53Tarballs
4. 13:38Stack-specific
5. 16:3205-Specific
6. 22:45Custom Images

" related talks

• 01h 04mDeploying and Scaling MicroservicesSam Newman · NDC Sydney 2016
• 37mKnee Deep in MicroservicesÁdám Sándor · MesosCon Europe 2017
• 01h 18mEmbracing Docker simplicity - while harnessing platform powerMichele Bustamante · NDC Sydney 2017
• 31mMicroservices and Docker at Scale: the PB&J of Modern Application DeliveryAnders Wallgren · DevOps Enterprise Summit San Francisco 2016
• 53mDocker as the Building Block for Datacenter-Scale ApplicationsBen Hindman · GOTO Amsterdam 2015
• 27mMicroservices Are ‘Easy’, Dependencies Are HardItiel Shwartz · Yalla DevOps 2021
• 33mEnabling MicroservicesSteve Hoffman · devopsdays Chicago 2015
• 01h 06mSo many Docker platforms, so little time...Michele Bustamante · NDC London 2017