In a distributed application, service-owning teams typically make decisions for their individual services, while application-wide concerns—such as shared infrastructure—need coordination. Smaller applications can handle architecture collectively; larger ones may warrant a separate architecture team. section 3.4.2 section 3.5
This team combines platform and enabling functions: it reduces development teams’ cognitive load with a platform that embodies the architecture and provides architectural consulting. Keep decisions primarily with development teams, and seek advice from affected people and relevant experts. section 3.4.2 section 3.5
Figure 3.18 The four options for who does architecture: benevolent dictator, architect in the team, architecture done by team members, and implicit architecture - image from https://architectelevator.com/architecture/organizing-architecture/
Compare this arrangement with other ways of organizing architecture work. section 3.4.2
