// 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.
3 rules of 70 · Clear filters
Ownership
- An owning team is named
One team owns the service end to end, and the design says which.
CriticalChecked automatically
- A runbook exists
The service has written steps for its most likely failures, so the person on call does not start from zero.
HighChecked automatically
- An on-call rotation or escalation contact is named
The design says who is reached, and how, when the service breaks outside office hours.
HighChecked automatically