An API makes operational promises as well as functional ones. An SLA formalizes one or more service-level objectives (SLOs) as contractual commitments to clients, often with penalties or credits for violations. section 8.1.3 section 8.4
Keep the related measures distinct:
- A service-level indicator (SLI) measures real-world behavior, such as latency, error rate, or uptime. section 8.1.3
- An SLO sets a target for an SLI; an SLA makes one or more SLOs contractual. section 8.1.3
Table 8.2 Some example SLOs for a service, each of which is a well-defined performance target
| SLO Type | Description | Example Target |
Availability |
Ensures that the API is reachable and functioning for consumers. |
At least 99.9% of requests succeed over a rolling 30-day period. |
Latency |
Measures how quickly the API responds to requests. |
95% of requests complete within 200 milliseconds. |
End-to-End Processing (Asynchronous) |
Measures how long it takes for published events to be processed by downstream consumers. |
99% of events are processed successfully within one minute. |
Data Freshness |
Ensures that derived views, caches, or replicas reflect recent updates. |
Replicated data is updated within 60 seconds of a change. |
These are example SLO targets, not necessarily contractual SLAs: availability, latency, asynchronous processing, and data freshness. section 8.1.3







