Principles for Building MicroServices
summary
Microservices require domain-driven, cohesive bounded contexts and true autonomy: each service runs as a standalone process with process-level isolation, owns its data (no centralized database), and avoids distributed transactions in favor of compensating transactions. Services expose technology-agnostic contracts, use circuit breakers to fail fast and preserve scale, and adopt automation and semantic versioning from day one so services can be rewritten or evolved affordably. Instrumentation uses correlation IDs for end-to-end traceability.
AI-written summary · about
chapters (13)
- 0:00Introduction and overview
- 2:21Monoliths versus microservices
- 6:13What microservices really are
- 10:11Principles for building microservices
- 17:10Cohesion and service size
- 23:17Autonomy and decoupling
- 28:58Database isolation and transactions
- 33:14Technology agnostic communication
- 36:04Decentralized governance
- 40:17Resilience and failure handling
- 44:39Automation and scalability
- 53:10Monitoring and correlation IDs
- 57:02Summary and key takeaways
related talks
49mDDD & Microservices: At Last, Some Boundaries!
01h 02mDesigning Microservices
57mBuilding Microservice Architectures
49mMicroservices: An unexpected Journey
52mWhat Does a Good Microservice Architecture Look Like?
40mMicroservices without DDD is risky business!
38mMicroservices, a bittersweet symphony
37mEvolutionary Architecture & Microservices