// 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
Ownership
- An owning team is named
One team owns the service end to end, and the design says which.
CriticalChecked automatically
Data
- No other service reads or writes its database
The service is the only thing that touches its tables. Everyone else goes through its API or its events.
CriticalChecked by hand
Resilience
- Hard dependencies have a timeout
Every synchronous call the service cannot work without has a declared timeout.
CriticalChecked automatically
Security
- Every caller is authenticated
The design says how the service knows who is calling, for users and for other services.
CriticalChecked automatically
- Secrets live in a secret store
Credentials and keys are read from a secret manager at run time, never from the repository or plain configuration.
CriticalChecked automatically