Chapter 85. You See Teams, I See Product
Avleen Vig
In 1967, Melvin Conway coined Conway’s Law, as follows:
Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization’s communication structure.
Over time, organizations have learned the value of not only having strong communication and collaboration between teams, but also of structuring it in specific ways. This becomes part of the team culture, and it instructs ICs on how to behave both as individuals and in groups.
Conway’s Law should be applied in reverse by organizations. Find the way you want your product to behave and create an organization whose communication structure emulates it. If your product has a high social factor, you probably want to encourage a lot of communication between teams. If your product is used in highly regulated industries, you may want to create a more process-driven, hierarchical organization.
The place you land on the spectrum between microservices and monolithic applications depends on how well the components in the system, and individuals on your teams, are able to communicate. If the interfaces are well designed, robust and resilient, and don’t change very often, you may lean toward microservices. If your team spends a lot more time trying to figure out the latest correct way to talk to each other and they have a high ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access