Site Reliability Engineering (SRE)
Make reliability a measurable, engineered outcome instead of a constant firefight.
Overview
Site Reliability Engineering applies software engineering to operations to make services reliable, scalable and efficient. We define service level objectives and error budgets that put a number on acceptable reliability, then use them to balance shipping features against stability. We automate toil, improve incident response and reduce the recurring failures that wake teams at 3am.
Methodology & Standards
Google SRE practices including SLOs and SLIs, error budgets and toil reduction, blameless postmortems, and incident-management practices aligned with NIST SP 800-61 for security-relevant incidents.
What's Included
What You Receive
Frequently Asked Questions
A service level objective is a target for reliability, such as 99.9 percent of requests succeeding. The gap between that target and 100 percent is your error budget. When the budget is healthy you can ship faster, when it is spent you focus on stability. It turns reliability into a shared, data-driven decision.
They overlap but differ in focus. DevOps is a broad culture for fast, reliable delivery. SRE is a specific, engineering-led implementation of reliability using SLOs, error budgets and toil reduction. Many organisations run SRE practices within a wider DevOps approach.