How would you apply Conway's Law to design team structures for microservices?
WHAT IT TESTS: Using org structure as an intentional architecture lever. ANSWER OUTLINE: Map bounded contexts to cross-functional teams; use APIs as contracts; split by decoupling boundary.
WHAT IT TESTS: Whether you treat Conway's Law as a design tool, recognizing communication paths become code coupling. ANSWER OUTLINE: Assign bounded contexts to cross-functional teams; design inter-team APIs to reflect communication and time zones; reject layer-based teams because they force PresentationDomainDataLayering; split teams at decoupling boundaries rather than fight the law. RED FLAG: Asserting architecture can be mandated without restructuring teams, or ignoring that remote locations and time zones harden API boundaries.
Read the original → martinfowler.com
- #conways-law
- #team-topologies
- #microservices
- #organizational-design
- #software-architecture
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.