Deploying and Scaling Microservices

on YouTube ↗01h 04m

" summary

Argues services must be independently deployable and use one artifact for all environments, showing concrete artifact options: tarballs (fragile), OS packages (deb/rpm via fpm), VM images (AMIs, built with Packer) and Docker containers (cheap isolation). Compares Docker Swarm (easy CLI but only recently gains rebalance), Mesos + Marathon (very mature, used to run Siri at ~30,000 nodes) and Kubernetes (Google-derived, pods and plaintext secrets quirk). Notes containers provision in milliseconds versus VMs in minutes.

AI-written summary · about

" chapters (4)

1. 0:00Start
2. 18:16Giant bundles of stuff
3. 31:36Independent Execution Environments FTW!
4. 42:37Docker Swarm

" related talks

• 51mDeploying And Scaling MicroservicesSam Newman · GOTO Chicago 2016
• 37mKnee Deep in MicroservicesÁdám Sándor · MesosCon Europe 2017
• 31mMicroservices and Docker at Scale: the PB&J of Modern Application DeliveryAnders Wallgren · DevOps Enterprise Summit San Francisco 2016
• 10mThe differences between microservices and containersTobias Knaup · Velocity 2017
• 33mEnabling MicroservicesSteve Hoffman · devopsdays Chicago 2015
• 23mMicroservices and containersVazha Pirtskhalaishvili · DevOps Inspire 2018
• 42mLessons Learned: Deploying Microservices Software Product in Customer EnvironmentsMark Galpin · MesosCon North America 2017
• 49mDeveloping microservices applications on the Kubernetes platformShahid Iqbal · NDC Sydney 2018