// 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.
6 rules of 70 · Clear filters
Observability
- Alerts are defined
The service has alerts on symptoms its users would notice, each one actionable.
HighChecked automatically
- An availability objective is set
The service has a stated availability target, so "is it reliable enough?" has an answer.
HighChecked automatically
- Consumer lag is monitored
The service measures how far behind its consumers are and alerts before the delay hurts users.
HighChecked by hand
- A p99 latency target is set
The service states how fast its slowest normal requests should be.
MediumChecked automatically
- Distributed tracing is on
Requests carry a trace context through the service, so one request can be followed across services.
MediumChecked automatically
- A dashboard exists
The service has a dashboard showing its traffic, errors and latency at a glance.
LowChecked automatically