SLA, SLO, and SLI definitions in HLD - System Design Guide

Problem Statement

Without clear agreements on service reliability, users face unpredictable downtime and poor performance. This causes frustration and loss of trust because expectations are not set or measured. Teams also struggle to prioritize fixes without measurable targets.

Solution

Define measurable indicators of service health (SLIs), set target levels for these indicators (SLOs), and formalize commitments to users (SLAs). This creates clear expectations and accountability. Teams can monitor SLIs against SLOs to maintain service quality and handle breaches according to SLAs.

Architecture

Service

→SLI

↓

Monitoring

→SLA

This diagram shows how a service's performance is measured by SLIs, which are compared against SLOs. Monitoring tracks these metrics, and SLAs formalize the commitments to users based on these targets.

Trade-offs

✓ Pros

→

Provides clear, measurable targets for service reliability and performance.

→

Aligns user expectations with engineering goals to reduce disputes.

→

Enables proactive monitoring and faster incident response.

→

Helps prioritize engineering efforts based on impact to users.

✗ Cons

→

Requires effort to define meaningful and measurable SLIs.

→

Setting unrealistic SLOs can lead to frequent breaches and loss of trust.

→

SLAs can create legal or financial risk if not carefully managed.

Use when operating services with external users or internal teams needing reliability guarantees, especially at scale with multiple stakeholders.

Avoid for small projects or prototypes where formal reliability targets add overhead without clear benefit.

Real World Examples

Google

Defines SLIs like request latency and error rate for services like Google Cloud, sets SLOs to maintain user trust, and uses SLAs to formalize uptime guarantees.

Netflix

Uses SLIs to monitor streaming quality and availability, sets SLOs to ensure smooth playback, and SLAs to manage customer expectations.

Amazon AWS

Publishes SLAs with uptime guarantees for services like EC2 and S3, backed by SLOs and SLIs tracked internally to maintain service health.

Alternatives

Error Budgeting

Focuses on the allowable error or downtime within SLOs to balance innovation and reliability.

Use when: Use when you want to manage risk tolerance and prioritize feature releases alongside reliability.

Service Level Management (SLM)

Broader ITIL-based process including SLA negotiation, monitoring, and reporting beyond just metrics.

Use when: Choose when managing multiple services with formal IT service management processes.

Summary

SLIs are specific metrics that measure service health and performance.

SLOs set target levels for SLIs to define acceptable service quality.

SLAs are formal agreements with users based on SLOs to set expectations and accountability.

Practice

1. What does SLA stand for in system design and what does it represent?

easy

A. Service Level Objective; a specific target for system reliability

B. Service Level Indicator; a metric to measure system performance

C. System Load Average; the average system load over time

D. Service Level Agreement; the overall service promise between provider and customer

Solution

1. Step 1: Understand SLA meaning

   SLA stands for Service Level Agreement, which is a formal contract or promise about the service quality.

2. Step 2: Identify SLA role

   It defines the overall service promise between the provider and the customer, including availability, performance, and support.

3. Final Answer:

   Service Level Agreement; the overall service promise between provider and customer -> Option D

4. Quick Check:

   SLA = overall service promise [OK]

Hint: SLA is the big promise, not the metric or target [OK]

Common Mistakes:

• Confusing SLA with SLO or SLI
• Thinking SLA is a metric
• Mixing SLA with system load terms

2. Which of the following correctly defines an SLI?

easy

A. A contract between provider and customer

B. A specific goal to meet the service promise

C. A metric used to measure service performance

D. A penalty for failing service levels

Solution

1. Step 1: Define SLI

   SLI stands for Service Level Indicator, which is a measurable metric that shows how well the service is performing.

2. Step 2: Differentiate from SLO and SLA

   Unlike SLO (goal) or SLA (contract), SLI is the actual measurement like latency, error rate, or uptime percentage.

3. Final Answer:

   A metric used to measure service performance -> Option C

4. Quick Check:

   SLI = metric [OK]

Hint: SLI is the number you measure, not the goal or contract [OK]

Common Mistakes:

• Confusing SLI with SLO or SLA
• Thinking SLI is a goal or agreement
• Mixing SLI with penalties

3. Given the following definitions:
SLA: 99.9% uptime per month
SLO: 99.95% uptime per month
SLI: Measured uptime percentage
What happens if the measured uptime is 99.92% for the month?

medium

A. SLA is met but SLO is violated

B. Both SLA and SLO are met

C. Both SLA and SLO are violated

D. SLA is violated but SLO is met

Solution

1. Step 1: Compare measured uptime with SLA

   The SLA requires 99.9% uptime. The measured uptime is 99.92%, which is higher, so SLA is met.

2. Step 2: Compare measured uptime with SLO

   The SLO target is 99.95%. The measured uptime 99.92% is less than 99.95%, so SLO is violated.

3. Final Answer:

   SLA is met but SLO is violated -> Option A

4. Quick Check:

   Measured uptime 99.92% < SLO 99.95% but > SLA 99.9% [OK]

Hint: Check if measured metric meets SLO first, then SLA [OK]

Common Mistakes:

• Mixing up SLA and SLO thresholds
• Assuming meeting SLA means meeting SLO
• Ignoring the difference between SLA and SLO

4. You have these definitions:
SLA: 99.9% uptime
SLO: 99.95% uptime
SLI: uptime percentage
Measured uptime is 99.85%. Which is the error in this statement?
"Since uptime is 99.85%, both SLA and SLO are met."

medium

A. The measured uptime is below SLA, so SLA is violated

B. The measured uptime is above SLO, so SLO is met

C. SLI is not uptime percentage

D. SLA and SLO are the same, so both are met

Solution

1. Step 1: Check measured uptime against SLA

   SLA requires 99.9% uptime. Measured uptime is 99.85%, which is less, so SLA is violated.

2. Step 2: Check measured uptime against SLO

   SLO requires 99.95% uptime. Measured uptime 99.85% is less, so SLO is also violated.

3. Final Answer:

   The measured uptime is below SLA, so SLA is violated -> Option A

4. Quick Check:

   99.85% < 99.9% SLA means SLA violated [OK]

Hint: Always compare measured uptime to SLA threshold first [OK]

Common Mistakes:

• Assuming 99.85% is above 99.9%
• Confusing SLI with SLO or SLA
• Thinking SLA and SLO are identical

5. A company promises 99.9% uptime in its SLA. It sets an SLO of 99.95% uptime and uses error rate as the SLI. If the error rate increases causing uptime to drop to 99.85%, what should the company do to maintain trust and meet SLA?

hard

A. Change the SLA to match the current uptime

B. Improve system reliability to reduce error rate below SLO target

C. Ignore the SLI since SLA is the only important metric

D. Increase the error rate threshold in SLI to match uptime

Solution

1. Step 1: Understand the relationship between SLA, SLO, and SLI

   SLA is the promise (99.9%), SLO is the goal (99.95%), and SLI is the metric (error rate) used to measure uptime.

2. Step 2: Analyze the impact of increased error rate

   Higher error rate lowers uptime to 99.85%, which violates both SLO and SLA targets, risking customer trust.

3. Step 3: Determine corrective action

   The company should improve system reliability to reduce error rate and restore uptime above SLA and SLO levels.

4. Final Answer:

   Improve system reliability to reduce error rate below SLO target -> Option B

5. Quick Check:

   Fix error rate to meet SLO and SLA [OK]

Hint: Fix the metric causing SLA breach, don't change promises [OK]

Common Mistakes:

• Changing SLA instead of fixing system
• Ignoring SLI importance
• Adjusting thresholds to hide problems