Forget monoliths vs. microservices. Cognitive load is what matters

During the research for our forthcoming book (Team Topologies: Organizing Business and Technology Teams for Fast Flow), and working with clients in different parts of the world, we realized that many organizations fail to consider an important dimension in the decisions around the size of software services: team cognitive load. Why you should use team cognitive load to right-size microservices
In a world of “You build it, you run it,” where the whole team is responsible for the successful operation of software services, it is imperative to remove unnecessary barriers to team ownership of software. Three ways to reduce team cognitive load and improve flow
There is no magic formula for reducing cognitive load for teams, but having worked with many large organizations around the world (including in China, Europe, and the US), we recommend three helpful approaches: well-defined team interaction patterns, independent stream-aligned teams, and a thinnest viable platform.

Source: techbeacon.com