// 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.
5 rules of 70 · Clear filters
Deployment
- At least two replicas run
The service runs as two or more instances, so losing one does not take it down.
HighChecked automatically
- Cutover is a routing change, not a release
Switching traffic between the old system and the new service is a configuration change that takes effect in minutes.
HighChecked by hand
- The way back to the legacy system has been rehearsed
The team has switched traffic back to the old system at least once, on purpose, and knows what happens to the data written meanwhile.
HighChecked by hand
- CPU and memory limits are set
Each instance declares how much CPU and memory it needs and may use.
MediumChecked automatically
- Traffic moves to the new version in steps
A release, or a cutover, reaches a small share of traffic first and grows only while the metrics stay healthy.
MediumChecked by hand