A journey to micro-services on Mesos
summary
Starts with a legacy VM monolith and ends with a Mesos platform running Docker containers orchestrated by Mesos+Marathon and service discovery via Consul. Builds a Calico network to give containers real IPs so Calico IP-per-container and local load‑balancers support blue-green deploys that drain long uploads. Claims: automated CI/CD, smaller microservices, faster feature delivery. Numbers: some proxies handle ~6 Gbps per container. Result: platform works but persistence and maintenance remain hard.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 0:46What is Mesos
- 1:14Dream Storage Cloud
- 1:34Popcorn Engineering
- 3:53Deployment
- 4:36Managing dependencies
- 6:24Team structure
- 7:20Software development
- 7:34Continuous delivery
- 11:22DrCompose
- 15:30Long Live Connections
- 16:33Team Transformation
- 17:34Platform Services
- 19:25Mesos Framework
- 22:40Marathon
- 24:08Platform overview
- 25:13Marathon deployment
- 25:38Console
- 26:56Service Discovery
- 30:34Service Failures
- 33:03PortGrupo de Saussure Marathon
- 34:36Assigning IPs
- 38:02Feature Development
- 39:12Persistence
- 40:44Maintenance
- 42:31Key Advantage
related talks
10mThe differences between microservices and containers
33mEnabling Microservices
37mKnee Deep in Microservices
24mFrom VMs To Containers: A DevOps Journey
33mContainer Networking for Micro-Services: An Apache Mesos Networking Deep Dive
45mContinuously delivering containerized, highly available microservices
42mUsing Mesos to Drive Devops Adoption at Scale
53mDocker as the Building Block for Datacenter-Scale Applications