Microservices Architecture & Monolith Migration
Monolith vs modular monolith vs microservices, DDD boundaries, data ownership, sync vs async, CQRS, event sourcing, strangler fig migration and the distributed-monolith trap
About 95 minutes · 15 exam questions · 9 interview questions · 2 code labs
What you will learn
- The architecture spectrum: monolith → modular monolith → microservices → functions
- Why evolve at all? Drivers, fitness functions and Conway's law
- Finding service boundaries with DDD bounded contexts
- Database per service and distributed data
- Communication: sync vs async, and service discovery
- The API gateway and BFF in a microservice landscape
- CQRS: separate the write model from read models
- Event sourcing: the log is the source of truth
- Contracts: versioning, consumer-driven contract tests and independent deploys
- Strangler fig migration: monolith → services without a big-bang rewrite
- The distributed monolith and other anti-patterns
Previous: Observability: Logs, Metrics, Traces & SLOs · Next: Deployment, Kubernetes & Release Strategies