// 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
Architecture
- Calls back to the legacy system are declared
Every call the new service still makes to the legacy system is listed as a dependency, with what it is for and how failure is handled.
MediumChecked by hand
- The replaced legacy code is removed
Once the new service carries all the traffic, the old code path, its data and its routes are deleted.
MediumChecked by hand