// 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
API
- API paths carry a version
Every REST path includes a version segment, so a breaking change can ship next to the old contract.
MediumChecked automatically
- Every endpoint is described
Each REST endpoint says what it does, so callers and coding agents do not have to guess from the path.
MediumChecked automatically
- The API is covered by contract tests
Tests check that the service still answers the way its consumers expect, and run before every release.
MediumChecked by hand