// 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
Resilience
- Hard dependencies have a timeout
Every synchronous call the service cannot work without has a declared timeout.
CriticalChecked automatically
- Hard dependencies have a circuit breaker or a fallback
When a dependency the service needs is failing, calls to it stop quickly or are answered another way.
HighChecked automatically
- Retries only on idempotent calls, with backoff and jitter
Retry a synchronous call only when repeating it is safe, and spread retries out so they don't pile onto a struggling dependency.
HighChecked by hand