Skip to main content

Reliability Basics for Site Reliability Engineers

Reliability basics explain what SRE is and why perfect uptime is the wrong goal. Embracing risk means choosing a target level of reliability that balances user needs against the cost of achieving it and the pace of feature releases. It forms the philosophical starting point of the SRE path.

Stage: Principles · Part of the Site Reliability Engineer roadmap · Last reviewed 19 November 2026

What to learn in Reliability Basics

Reliability Basics interview questions

Why not aim for 100 percent availability?

The cost rises steeply with each extra nine, users often cannot notice the difference past a point because their own network and devices are less reliable, and chasing perfection blocks change. A deliberate target leaves room to ship features safely.

How is SRE different from DevOps?

DevOps is a cultural movement for closer development and operations collaboration. SRE is a concrete implementation with defined practices such as SLOs, error budgets and toil limits, and with engineers who write code to run services. Many see SRE as one way of doing DevOps.

Where Reliability Basics fits in the Site Reliability Engineer roadmap

Reliability Basics belongs to the Principles stage (intermediate level), which takes about 40 hours. How SRE thinks about reliability.

Back to the full Site Reliability Engineer roadmap