// RULES
Microservice rules
Best practices for microservices, one rule per page: why it matters, how to apply it and an example. They are grouped into checklists you can apply to a service.
2 rules of 70 · Clear filters
Observability
- A dashboard exists
The service has a dashboard showing its traffic, errors and latency at a glance.
LowChecked automatically
Decisions
- Key decisions are recorded
At least one architecture decision is written down and accepted, with its context and consequences.
LowChecked automatically