liveBook · Manning

Service-level agreement

As explained in Microservices Patterns, Second Edition

A service-level agreement is a documented commitment that defines expected, measurable service levels and associated obligations or consequences.

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

How Microservices Patterns, Second Edition covers it

How deep it goes
Distinguishes SLAs from SLIs and SLOs, but does not detail contract design or enforcement.
Examples
Uses availability, latency, asynchronous processing, and data freshness targets as examples of measurable service objectives.
What you can do after
Evaluate the distinction between measured indicators, desired objectives, and contractual commitments.
How it connects
Connects service-level agreements to service-level objectives, service-level indicators, observability, and error budgets.

Also explained in

Compare how 8 books explain service-level agreement →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.