The big picture, from two sides
Each pattern solves one problem. These guides show how they fit together. A microservice system has a technical side, the layers it is built from, and an organisational side, the teams that build and run it. They are separate questions, and most trouble comes from mixing them up.
- Architecture · How is the system built?
Layers and cross-cutting concerns
Every layer from the screen to the database, who owns it, and how concerns such as identity, tracing and versioning work across all of them.
The technical side: where service boundaries go, how services share data and talk, how web and mobile clients fit in, how the system survives failure, and the platform it runs on.
40 patterns · Read the guide → - Organisation · Who builds and runs it?
Teams and ownership
Product teams through every layer, platform teams under them, the four team types and who usually owns each pattern.
The people side: how teams are shaped around business capabilities and the platform, how they work together, and who owns each pattern.
7 patterns · Read the guide →