SLA, SLO, and SLI definitions in HLD - Scalability & System Analysis

Scalability Analysis - SLA, SLO, and SLI definitions

Growth Table: SLA, SLO, and SLI Definitions

Scale	What Changes?
100 users	Basic SLIs measured manually or with simple tools; SLOs set loosely; SLA agreements informal or simple.
10,000 users	Automated monitoring for SLIs; SLOs become formal targets; SLAs documented with penalties; alerting systems introduced.
1,000,000 users	High precision SLIs with real-time dashboards; strict SLOs with error budgets; SLAs legally binding; multi-region monitoring.
100,000,000 users	Distributed SLIs across services; dynamic SLO adjustments; SLAs include complex compliance; advanced anomaly detection.

First Bottleneck

At small scale, the main bottleneck is lack of precise measurement tools for SLIs, causing unclear SLOs and SLA enforcement.

As scale grows, bottlenecks shift to monitoring infrastructure capacity and data aggregation delays, making real-time SLI tracking difficult.

Scaling Solutions

• Automate Monitoring: Use scalable monitoring tools (e.g., Prometheus, Datadog) to collect SLIs efficiently.
• Distributed Tracing: Implement tracing to measure SLIs across microservices.
• Alerting and Error Budgets: Use SLO-based alerting to focus on meaningful issues.
• Data Aggregation: Use time-series databases and aggregation to handle large volumes of SLI data.
• Legal and Compliance: Scale SLA management with contract automation tools.

Back-of-Envelope Cost Analysis

For 1 million users generating 100 requests per second (RPS):

• Monitoring system must handle 100 million RPS metrics collection plus aggregation.
• Storage for SLI data: assuming 10 metrics per request, 100 million RPS * 10 metrics * 86400 seconds/day ≈ 86 trillion data points/day.
• Bandwidth for monitoring data: ~10 KB per metric point -> ~860 PB/day.
• Costs grow with retention period and granularity of SLIs.

Interview Tip

When discussing SLA, SLO, and SLI scalability, start by defining each term clearly.

Explain how measurement precision and monitoring infrastructure evolve with scale.

Discuss bottlenecks in data collection and aggregation, then propose automation and distributed monitoring solutions.

Use real numbers to show understanding of volume and cost impact.

Self Check

Your database handles 1000 QPS for storing SLI data. Traffic grows 10x to 10,000 QPS. What do you do first?

Answer: Introduce caching and aggregation to reduce write load, then add read replicas or partition the database to handle increased QPS.

Key Result

SLI measurement and monitoring infrastructure become the first bottleneck as user scale grows; automating and distributing monitoring is key to scaling SLA and SLO management.

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