DevOps Intermediate

What is SRE (Site Reliability Engineering)?

An engineering discipline that applies software engineering principles to infrastructure and operations to create reliable systems.

Site Reliability Engineering, pioneered by Google, treats operations as a software problem. SRE teams define Service Level Objectives (SLOs), measure them through Service Level Indicators (SLIs), and use error budgets to balance reliability with feature velocity. When the error budget is exhausted, teams prioritize reliability work over new features. Key practices include toil automation (eliminating repetitive manual work), blameless postmortems, capacity planning, and progressive rollouts. SRE bridges the gap between development speed and operational stability.

Learn More About This Topic

Kubernetes for Production: Scaling & Monitoring

Related reading

n8n CLI for Beginners

Related reading

Webhook Automation in Practice

Related reading

Related Terms

A deployment strategy that gradually replaces old application instances with new ones, maintaining availability throughout.

Containerization

A lightweight virtualization method that packages applications with their dependencies into isolated, portable containers.

A technique that allows enabling or disabling features in production without deploying new code, enabling safe rollouts and A/B testing.

A server that acts as the single entry point for API requests, handling routing, authentication, rate limiting, and monitoring.

A file containing build rules and commands that automates compilation and common project tasks using the make utility.

The practice of collecting, analyzing, and alerting on system metrics and logs to ensure application health and performance.

View All DevOps Terms →