SRE vs DevOps: Can they coexist or do they compete?
Systems fail, sometimes publicly and at great cost. Airlines have experienced system-wide ticketing outages, causing hundreds of flight cancellations and significant inconvenience to customers. Retailers have experienced website crashes on the busiest shopping days of the year, costing millions in lost revenue and customer goodwill.
It is vital to understand both DevOps and SRE and the roles they play in preventing such outages.
Thanks for requesting SRE vs DevOps: Can they coexist or do they compete?! View the whitepaper here. (A copy has also been sent to your email.)
About the Authors
In this eBook, we cover:
- What DevOps is and how it works, including success metrics and tools
- What Site Reliability Engineering (SRE) is and how it can prevent incidents
- How DevOps and SRE compare and whether both are needed to succeed in today's high velocity environments
Incident classification: SEV descriptions and levels, and SEV and time-to-detection (TTD) timelines
Organization-wide critical service monitoring, including key dashboards and KPI metrics emails
Service ownership and metrics for organizations maintaining a microservices architecture
Effective on-call principles for site reliability engineers, including rotation structure, alert threshold maintenance, and escalation practices
Chaos Engineering practices to identify random and unpredictable behavior in your system
Monitoring and metrics to detect incidents caused by self-healing systems
Creating a high-reliability culture by listening to people in your organization
Can we prevent outages in an era of such great velocity? We have gone from annual software releases to daily releases, from running software as a monolith to running hundreds of microservices, from on prem hosting on hundreds of physical hosts to Kubernetes, containers, and cloud hosts numbering sometimes into the hundreds of thousands.