Unraveling the Differences
summary
Compares SRE, DevOps and platform engineering by giving concrete practices and tools: SLOs/SLIs with an example 99.95 SLO and an error budget of ~20 minutes over 28 days, explicit use of OpenTelemetry and Azure Monitor for distributed tracing and observability, plus Bicep/Terraform/Pulumi for infra as code, feature flags (LaunchDarkly/Azure App Configuration), Canary/blue‑green deployments, Trivy/terrascan scanning, and postmortem-driven incident workflows that stop feature work when the budget is exhausted.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:30Dev versus Ops divide
- 3:18Site Reliability Engineering
- 5:27Reliability and error budgets
- 7:34Observability and error budgets
- 10:28Reducing toil with automation
- 12:39Feedback loops and improvements
- 15:12Measuring reliability and failures
- 19:02On-call and incident management
- 20:51Blameless postmortems
- 23:20Trust and transparency culture
- 25:27Release strategies
- 29:24DevOps principles
- 32:57Breaking silos
- 35:21Conway's law
- 36:27Shift left security
- 37:12CI/CD and IaC
- 39:41Configuration management
- 41:26DevSecOps
- 43:32Microservices Kubernetes
- 44:14Platform engineering
- 46:47Simplicity and iteration
- 48:38Unifying SRE DevOps platform
- 49:00Q&A
related talks
42mDemystifying SRE and DevOps
43mWhere SRE Can Go Wrong
08mSRE vs DevOps: The Difference & Why It Matters
39mSRE or Devops - I am an Architect - Why Do I Care?- 42mDemystifying SRE and DevOps
27mGetting Started with SRE
47mDevOps or DevX – Lessons We Learned Shifting Left the Wrong Way
22mSRE for Enterprises