Service Level Objective (SLO): A Measurable Promise
An SLO is a precise, measurable promise about your service's performance, like "99.9% of requests will succeed." It's the internal engineering target that backs up a customer-facing SLA. The footgun is setting a 100% SLO, which leaves no room for failure.
Why it exists
To move beyond vague promises like "the service should be reliable." SLOs provide a specific, quantitative target for engineering teams to build and operate against, creating a shared understanding of what "good enough" means and aligning business and technical stakeholders.
The mental model
Think of an SLO as a promise you make to your users, but written as a number for your engineers. It's the target on the wall. The SLI (Service Level Indicator) is the metric you use to measure where your shots land. The SLA (Service Level Agreement) is the business contract that might specify consequences, like refunds, if you miss the target too often.
How it works
You start by choosing a critical user journey, like "checking out a shopping cart." Then you pick a metric to measure it—the SLI, such as the percentage of successful checkout API calls. Finally, you set a target for that metric over a time window. For example: "99.95% of checkout requests over a rolling 30-day period will complete successfully in under 3 seconds." This target is the SLO. The remaining 0.05% is your "error budget"—the amount of failure you can tolerate before violating your objective.
When to use it
Use SLOs to make data-driven decisions about priorities. They provide a clear signal for when to focus on shipping new features versus when to pause and improve stability. If you have consumed your error budget for the month, all work might shift to reliability until the service is back within its SLO.
When not to use it
Avoid creating SLOs for every single metric. This creates noise and alert fatigue. Focus on the few key indicators that directly represent the user's experience of availability, latency, or correctness. An SLO on an internal database's CPU usage is less useful than one on user-facing API response time.
One canonical example
A media streaming service wants to ensure a good playback experience. They define an SLI as "playback availability," measured by the percentage of times a user clicks play and the video starts successfully. They set an SLO of 99.9% availability over a 28-day window. If availability drops to 99.8%, they have violated their SLO and must prioritize fixing the underlying issues.
Interview question
What is the primary purpose of defining a Service Level Objective (SLO) for a service?
- a.To establish a legally enforceable contract with customers regarding service availability and performance.
- b.To provide a clear, measurable target that guides engineering efforts and aligns stakeholders on service quality.Correct
- c.To ensure that the service achieves 100% reliability and uptime for all user interactions.
- d.To monitor every internal system metric to detect any potential performance degradation.
Why? this is the answer
The card states that SLOs "provide a specific, quantitative target for engineering teams to build and operate against, creating a shared understanding of what 'good enough' means and aligning business and technical stakeholders." Option A describes an SLA, not an SLO, and options C and D contradict the card's advice on avoiding alert fatigue and 100% SLOs.
Just read this? Test yourself on what you have been reading.
Read the original → en.wikipedia.org
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on reliability — each one lists the topics its interview covers.
See open roles