liveBook · Manning

Service-level agreement

As explained in Grokking Software Architecture

A service-level agreement is a formal commitment defining expected service performance and availability between a provider and a customer.

An SLA is a legally binding commitment that sets expected service levels between a provider and its customers. For resilience planning, its latency guarantee can help set timeouts; historical monitoring data makes those thresholds defensible rather than guesswork. section 10.2.1

Turn a promise into a threshold

If an API promises that 95% of requests finish within 500 milliseconds, use that latency guarantee to guide timeout settings. A monitoring baseline showing 99% of healthy requests finish within two seconds can also support a two-second timeout. section 10.2.1

How Grokking Software Architecture covers it

How deep it goes
Defines contractual service expectations and explains how latency guarantees guide timeout choices.
Examples
Uses a 95%-within-500-milliseconds API promise and a 99%-within-two-seconds monitoring baseline.
What you can do after
Configure timeout thresholds using SLA latency guarantees and historical monitoring baselines.
How it connects
Connects uptime and latency guarantees to timeouts and vendor accountability.

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 Grokking Software Architecture. The section links point to the parts of the book it draws on.