From Monolith to Microservices with Kubernetes and Linkerd
summary
Starts from a seven‑year PHP monolith and incrementally adopts Docker, Consul, Linkerd and Kubernetes, first running 15 services across 20 servers with Salt + Supervisor, then moving routing to Linkerd talking to Consul and Kubernetes to eliminate manual VIPs and TLS pain. Chooses the kismatic installer for bare metal, uses Helm for consistent deploys, Vault for secrets and a custom deploy tool for security. Linkerd adds minimal latency, removes hardware load balancers, and the plan scales to hundreds of services.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:53Why Microservices
- 2:41Baby Steps
- 5:11Deployment Tools
- 7:01Service Discovery
- 8:07Dynamic Routing
- 12:34Orchestration
- 19:18Running Services
- 24:10Questions
- 32:30Data migrations
related talks
39mGrow with Less Pains - Meshing From Monolith to Microservices
48mFrom Monolith to Micro-services with Kubernetes
35mDeep Dive: Linkerd
36mOverview and State of Linkerd
18mRe-Architecting Monoliths Into Kubernetes Microservices at Million-User Scale: Hard...
24mFrom Monolith to Microservices: A Journey into the Mesh
35mNavigating the Service Mesh Ecosystem
01h 10mService Mesh Introduction