Conway's law says that an organization designing a system tends to produce a system whose structure mirrors how its people communicate. The architecture reflects the team boundaries and coordination patterns behind it. section 12.2.3 section 12.11
A small team can coordinate around one monolith. As an organization grows, teams sharing one codebase may wait on one another to deploy. Microservices can give teams independent release schedules—but they address a human scaling problem, not simply a need for faster code. section 12.2.3 section 12.11
When teams share a deployment queue
Imagine an organization of 500 developers across time zones. If the Inventory Team's release depends on the same monolith deployment as the Billing Team's work, a delay or broken build can hold both teams up. Independent microservice deployments can reduce that coordination bottleneck. section 12.2.3
Use organizational scale as a guide, not a reason to split a system automatically:
- For a team of 5–15 developers, favor a monolith when communication is easy. section 12.2.3
- Consider microservices when a large organization needs teams to release independently; otherwise, their operational overhead may be self-defeating. section 12.2.3 section 12.11

