A Field Guide to Reliability Engineering at Zalando
summary
Zalando runs reliability for ~50M customers across 25 countries with ~3,000 microservices and ~2,000 engineers and uses OpenTelemetry and a homegrown observability SDK to ship traces since 2019, generate SLI/SLOs (about 100 SLOs, 7‑day and 28‑day SLIs, examples like browse/catalog ~3.5 nines), and route alerts via adaptive paging. Teams build symptom‑based alerts, curated dashboards, postmortems and risks, hold a weekly 1‑hour operational review with directors, and track ~10 incidents/week to steer investments.
AI-written summary · about
chapters (12)
- 0:00Intro
- 3:45Agenda
- 4:04Principles
- 10:32Context
- 14:44Operations at Zalando
- 21:25Dashboards
- 24:32Observability
- 31:51SLOs
- 37:32Incident process
- 45:20WORMs
- 50:01Summary
- 50:37Outro
related talks
24mMeatbag Systems: How Our Reliability Culture & Practice...
37mIntroducing Reliability Toolkit: Easy-to-Use Monitoring and Alerting
20mBuilding a Culture of Reliability
44mReliability at 45M Customers — Tools and Practices of a Digital Bank
30mReliability Engineering for Humans
26mTechnology and Cultural Transformation using Site Reliability Engineering
45mEngineering resiliency - how I learned to love an outage
35mIs My Thing Reliable? Adventures in Driving Consistency of...