DataTerminology.comNEW
Also known as: SRE
An engineering discipline applying software practices to operations to build reliable, scalable, and efficient services.
DESCRIPTION
Site Reliability Engineering blends software engineering with operations to achieve reliability, scalability, and agility. SRE practices include defining SLOs/SLIs, managing error budgets, reducing toil, automation, robust on-call, incident response, and blameless postmortems. It emphasizes measuring reliability, using risk to pace change, and engineering solutions over manual ops. Originating at Google, SRE is now widely adopted across enterprises and cloud-native teams.
ALTERNATIVE DEFINITIONS
Google Cloud
Site Reliability Engineering (SRE) is a discipline that incorporates aspects of software engineering and applies them to infrastructure and operations problems.
Centers on applying software engineering to operations challenges.
Google SRE Book
SRE is what happens when you ask a software engineer to design an operations function.
Captures SRE’s engineering-first approach to operations.
RELATED TERMS
Service Level Objective SLA Error Budget Incident Management On-call Postmortem Observability Runbook Toil
COMPETING TERMS
RELATIONS
- Broader: Reliability Engineering
KNOWLEDGE AREAS
Observability & Telemetry Software Engineering MLOps Cloud Collaboration Testing & Validation
TARGET AUDIENCE
DevOps Engineer IT Manager Chief Technology Officer Cloud Architect Software Developer Application Administrator Security Architect Chief Information Officer
EXTERNAL SOURCES
- Wikipedia - Site reliability engineering
- Google SRE Book - Foundational practices and principles
- USENIX - SRE-focused conference proceedings
TOP QUESTIONS
Why is Site Reliability Engineering important?
SRE makes reliability measurable and actionable, enabling faster delivery with controlled risk through SLOs, error budgets, and automation.
Category: Relevancy
How do SRE and DevOps differ?
DevOps is a cultural movement; SRE operationalizes it with concrete practices, metrics, and roles to achieve reliability.
Category: Misunderstanding
What is a core SRE practice?
Defining SLIs/SLOs and using error budgets to balance reliability and velocity is central.
Category: Example
What is a common mistake in SRE adoption?
Skipping SLOs and jumping straight to tooling undermines focus and alignment on user-centric reliability.
Category: Mistakes
How does SRE handle incidents?
SREs prioritize fast detection, effective on-call, and blameless postmortems to learn and prevent recurrences.
Category: Management
What is currently a hot topic in SRE?
Adaptive SLOs, AI-assisted incident response, and platform SRE for internal developer platforms are trending.
Category: Topic
Which metrics matter most in SRE?
SLIs like availability, latency, and correctness align engineering work with user experience.
Category: Requirements
How does SRE reduce toil?
By automating repetitive operational tasks and investing in self-service platforms to scale reliability.
Category: Example
Where should organizations start with SRE?
Establish SLOs for critical services, measure SLIs, adopt error budgets, and automate high-toil tasks first.
Category: Requirements