Monolith vs. Microservices
5 exercises — practise the vocabulary of monolith-to-microservices discussions: the strangler fig migration pattern, bounded context from DDD, Conway's Law and the Inverse Conway Maneuver, operational overhead specifics, and the modular monolith recommendation.
Monolith vs. microservices quick reference
- Strangler fig: incremental migration — route specific capabilities to new services while monolith continues operating; avoids big-bang rewrite
- Bounded context: DDD concept — a domain model is valid and consistent within a context boundary; the same word can mean different things in different contexts
- Conway's Law: "systems mirror the communication structure of the organisations that build them"
- Inverse Conway Maneuver: deliberately restructure teams to produce the architecture you want
- Operational overhead: service discovery, distributed tracing, inter-service auth, multiple pipelines, distributed transactions
- Modular monolith: architectural discipline without distributed systems complexity — extractable later when scale demands it
Question 1 of