The 36th Chamber of Shaolin – Improve Your Microservices Kung Fu in 36 Easy Steps
summary
36 concrete steps claim covers architecture and ops choices actually used: a mono-repo, gRPC / Protocol Buffers for internal RPC, Kubernetes clusters for deployment, Canary releases and replica autoscaling. Targets include 10s startup for services and tight response-time SLOs (100ms class for critical paths). Implemented monitoring ties requests to backend components for debugging; idempotent APIs, context deadlines and retries replace distributed transactions. Reported outcomes are fewer rollout failures and faster iteration when canaries and metrics catch regressions early.
AI-written summary · about
chapters (15)
- 0:00Microservices and Shaolin metaphor
- 3:28Core microservices principles
- 7:10Memory footprint challenges
- 10:59Real-time microservice monitoring
- 14:24Sync vs async communication
- 18:04Protocol buffers in services
- 21:50Debugging distributed systems
- 25:07Integration testing microservices
- 28:50Versioning strategies
- 31:36Cluster management
- 33:20Mobile client optimization
- 35:34Load balancing
- 37:04Operations and reliability
- 38:50Downtime budget
- 39:59Q&A
related talks
37mKnee Deep in Microservices
30mHow to Fail at Building Modern Microservices
28mFour Pillars and a Base: The Nuts and Bolts of a Microservice-based Project
57m6 Lessons I Learned on My Journey from Monolith to Microservices
24mPatterns of Evolution from Monolith to Microservices
48mFrom Monolith to Micro-services with Kubernetes
57mEmbracing Microservices
52mTools to Slay the Fire Breathing Monoliths in Your Enterprise - Kelapure, Anderson, Szodfridt