Finding Service Boundaries & Splitting the Monolith
Information hiding, bounded contexts and the strangler fig. Lesson 2 of Level 9: Microservices.
Level 9 · Microservices · Lesson 2 of 13
Information hiding, bounded contexts and the strangler fig.
Continue learning
- Why Microservices Exist — and When Not to Use Them — Previous lesson
- Database per Service & Data Ownership — Next lesson
- Level 9: Microservices — Back to the level
Try it hands-on
- DDD Bounded Contexts Workshop — Sort ShopFlow concepts into bounded contexts, see where “Customer” and “Product” mean different things, and check coupling.
All lessons in Microservices
- Why Microservices Exist — and When Not to Use Them
- Finding Service Boundaries & Splitting the Monolith
- Database per Service & Data Ownership
- Synchronous vs Asynchronous Communication
- API Gateways, BFFs & Service Discovery
- Timeouts, Retries & Retry Storms
- Circuit Breakers & Bulkheads
- Idempotency: Making Retries Safe
- Distributed Transactions: 2PC, Sagas & the Outbox
- Observability: Logs, Metrics, Traces & SLOs
- Deployment: Containers, Kubernetes, Canary & Feature Flags
- Testing Microservices & Consumer-Driven Contracts
- Teams, Ownership & Conway’s Law