liveBook · Manning

Service-level objective

As explained in Microservices Patterns, Second Edition

A target value for a service-level indicator that expresses a desired level of reliability or performance.

A service-level objective (SLO) is a target value for a service-level indicator (SLI), expressing a desired level of reliability or performance. It turns an API’s operational promise into a measurable target: the SLI measures behavior, and the SLO states the desired result. A service-level agreement (SLA) adds a contractual commitment, often with penalties or credits for violations. section 8.1.3 section 8.4

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.

Example targets cover availability, latency, asynchronous processing and data freshness. section 8.1.3

An objective needs observability to be useful. Instrument APIs to collect the metrics that drive SLIs, and compare telemetry against targets to detect reliability issues. An error budget expresses the unreliability allowed without breaching SLOs; it helps teams decide whether to prioritize feature development or service reliability. section 8.1.3 section 8.4

Latency versus team autonomy

Suppose separating Order Management and Consumer Management causes createOrder() to exceed its latency SLO. Teams can accept the latency and its effect on user experience, or combine the subdomains so the operation can meet its target. Combining them reduces team autonomy because changes and deployments require coordination. Network communication cost alone is not decisive if the operation still meets its SLO. section 7.5.1

Timeouts and consistency

A saga that waits indefinitely for a participant might miss a system command’s execution-time SLO. A timeout can allow the command to meet the target, but a missing response does not reveal whether the participant acted. If a credit reservation might have succeeded, rejecting the order also requires a cancellation request to avoid leaving inconsistent state. section 9.2.3

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines objectives and related terms, gives targets and trade-offs, and defers detailed observability practices and tooling.
Examples
Illustrates availability, latency, asynchronous processing and data-freshness targets, plus order-service latency and saga timeout scenarios.
What you can do after
Evaluate distributed-service and timeout choices against objectives and their operational trade-offs.
How it connects
Connects service-level indicators, service-level agreements, observability, error budgets and saga timeouts.

Also explained in

Compare how 4 books explain service-level objective →

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.