DevOps Conference
The Conference for Continuous Delivery, Microservices,
Containers, Clouds and Lean Business

Working up the Hierarchy of Service Reliability

Session
This talk originates from the archive. To the CURRENT program
Until October 31: ✓ Group Discount ✓ Save up to 375 € Register now
München: Bis 31. Oktober ✓ Kollegenrabatt
✓ Bis zu 375 € sparen Jetzt anmelden
Until October 31:
✓ Group Discount
✓ Save up to 375 €
Register now
Bis 31. Oktober
✓ Kollegenrabatt
✓ Bis zu 375 € sparen
Jetzt anmelden
Until December 12:
✓ Workshop Day for free
✓ Raspberry Pi or C64 Mini for free
✓ Save up to $690
Register now
Until December 12:
✓ Workshop Day for free
✓ Raspberry Pi or C64 Mini for free
✓ Save up to $690
Register now
Until November 28:
✓ Transformation Day for free
✓ Raspberry Pi or C64 Mini for free
✓ Save over £689
Register Now

Until November 28:
✓ Transformation Day for free
✓ Raspberry Pi or C64 Mini for free
✓ Save over £689
Register Now

Until March 5:
✓ Transformation Day for free
✓ Raspberry Pi or C64 Mini for free
✓ Save over 850 €
Register now
Bis 5. März:
✓ Transformation Day for free
✓ Raspberry Pi oder C64 Mini for free
✓ Über 850 € sparen
Jetzt anmelden
Until June 18:
✓ Workshop Day for free
✓ Raspberry Pi or C64 Mini for free
✓ Save over $840
Register now
Until June 18:
✓ Workshop Day for free
✓ Raspberry Pi or C64 Mini for free
✓ Save over $840
Register now

More talks in the program:

Infos
Wednesday, May 30 2018
12:00 - 13:00
Room:
MOA 6

When former Google SRE Mikey Dickerson had to explain to outsiders the Google way of increasing a site’s reliability, he came up with his famous “Hierarchy of Service Reliability”, modeled on Maslow’s even more famous “Hierarchy of Needs”. In Dickerson’s hierarchy, the base is monitoring, and the actual product is at the very top, with a number of layers in between. It is one of the most meaningful illustrations in O’Reilly’s book about “Site Reliability Engineering: How Google Runs Production Systems”. SoundCloud’s journey to a reliable site essentially meant climbing up that hierarchy. However, we had to learn – often the hard way – that we could not just copy Google’s SRE practices directly. We found ourselves applying “SRE in spirit” but adjusting the implementation details to the scale and culture of our organization. Since SoundCloud also follows a very radical school of DevOps, our story contains a good amount of productive cross-pollination between SRE and DevOps.

Stay tuned:

Behind the Tracks

 

Kubernetes Ecosystem

Docker, Kubernetes & Co

Microservices & Software Architecture

Maximize development productivity

Continuous Delivery & Automation

Build, test and deploy agile

Cloud Platforms & Serverless

Cloud-based & native apps

Monitoring, Traceability & Diagnostics

Handle the complexity of microservices applications

Security

DevSecOps for safer applications

Business & Company Culture

Radically optimize IT

Organizational Change

Overcome obstacles on the way towards DevOps

Live Demo #slideless

Showing how technology really works