In this chapter, we've looked at the different aspects of coordination across teams so that we can successfully manage an organization running a microservice architecture.
We started by talking about how keeping a global vision and coordination between parts is good. We talked about having an explicitly named leading architect that oversees the system and has a high-level view that allows them to ensure that teams aren't conflicting with each other.
We described Conway's Law and how the communication structure ends up shaping the software's structure so any change made to the software should be reflected somehow in the organization and vice versa. Then, we learned how to divide areas of responsibility and provided some examples of possible divisions, based on different organizations.
Next, we introduced how technical debt slows down the ongoing development...
