Building Microservice Architectures
summary
Explains how microservices use domain-driven bounded contexts and continuous delivery to make change cheap, with concrete tradeoffs: a config service handling 1,000 TPS with 99th‑percentile < 2s, a user service serving 100M active customers, and a raw transaction store ingesting 30–90M nightly records under PCI‑Level 1. Covers tooling (Puppet/Chef, Docker, Consul/Zookeeper, Dropwizard/Spring Boot, ELK), patterns (feature toggles, synthetic transactions, correlation IDs, circuit breakers), and when to prefer larger service slices or preserve transactional context.
AI-written summary · about
chapters (20)
- 0:00Introduction to microservices
- 1:11Service-oriented architecture explained
- 6:48Domain-driven design influence
- 9:38Bounded context in microservices
- 13:31Post-devops revolution architecture
- 17:44Smart endpoints and dumb pipes
- 20:52Decentralized data management
- 25:52Evolutionary architecture benefits
- 29:42Handling high-volume services
- 33:55Feature toggles and AB testing
- 37:04Designing for failure
- 40:12Synthetic transactions
- 43:45Shared nothing architecture limits
- 45:10Service templates for consistency
- 47:19Orchestration vs choreography
- 49:46Deployment strategies
- 51:54Service discovery tools
- 53:57Maturity prerequisites
- 55:01Service-based architecture hybrid
- 56:46Conway's law and team structure
related talks
01h 00mPrinciples for Building MicroServices
01h 02mDesigning Microservices
38mMicroservices, a bittersweet symphony
54mThe Long Sad History of Microservices
52mWhat Does a Good Microservice Architecture Look Like?
56mMicroservices and Domain-Driven Design — The Strategic Parts
48mChallenges in Implementing MicroServices
37mKnee Deep in Microservices