Bottoms-Up Adoption of a Microservices Workflow Using Kubernetes & Envoy
summary
Claim: velocity comes from changing the process not the architecture. Practical stack: package language-specific build toolchains into Docker images so each docker build produces the runnable artifact, deploy branch environments into a single Kubernetes cluster for branch-isolated deployments, use Ambassador annotations to route to back‑ends via Ambassador+Envoy gateway, cache builds and shortcut image builds with a Forge-like tool, and provide self‑service deploys and observability; applied across 30–40 customer engagements and cut developer friction dramatically.
AI-written summary · about
chapters (11)
- 0:00Start
- 3:53Early History
- 9:17Software Stability versus Velocity
- 10:10Development Process
- 12:46Organizational Factors
- 15:41Technical Implementation
- 20:26Design Considerations
- 28:14Kubernetes Journey
- 31:02Step Two You Have To Provide Fast Self Service Deploy
- 32:57Step Three You Have To Make It Easy To Reach the Changed Code
- 35:24Summary
related talks
32mHow Lyft Used Envoy to Rethink Microservice Development
45mHow Kubernetes Was the Secret Sauce in Our Globally Distributed Team’s Transition to Microservices
33mLevel Up Your Developer Experience 🧭
51mMoving at the Speed of Thought
18mMulti-environment deployment for K8s-based microservice arch
29mK8s Complexity Tamed: One Interface To Rule Them All With CNCF Incubat...
34mArchitektury Aplikacji: The last mile of microservices
40mDeploying Micro Frontends to a Kubernetes Cluster