// 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.

28 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

Events

Data

Observability

  • A p99 latency target is set

    The service states how fast its slowest normal requests should be.

    MediumChecked automatically

  • Distributed tracing is on

    Requests carry a trace context through the service, so one request can be followed across services.

    MediumChecked automatically

Security

Deployment

Architecture