Path to SRE

You’ve heard all the buzz about SRE, but what does it actually take to do it if you are not Google? In this talk you will learn about our experience creating Auth0's SRE flavor and rolling it out.

Transcript

1. The Path to SRE @dschenkelman Director of Engineering @auth0
2. SRE
3. Why?
4. Reliability is the one feature every customer uses - an @auth0 SRE
5. Auth0 User Auth0 Customer App
6. Context
7. Focused Investment Like Security but for Reliability
8. Scale
9. Research
10. Companies
11. Organizations
12. Style
13. Sponsors
14. Who?
15. Spectrum Systems Software
16. The Usual Suspects
17. Teachers
18. Advocates
19. Problem solvers
20. Know the system
21. Experience
22. node.js
23. Educate
24. What we do SRE identifies, develops, refines, and disseminates the libraries, services, practices, and processes key to system reliability.
25. SRE does not force itself on other teams
26. SRE does not handle all incident response
27. Involvement Spectrum SRE Run Service Embedding Consultancy Office Hours/ Workshops
28. Contacting SRE
29. The brand
30. Logo
31. Office Hours
32. Brown bags
33. Investigations
34. Flexibility
35. Incidents
36. Execute!
37. You are selling TRUST
38. SLOs
39. R2
43. Incident Response
44. Distributed Traces
45. Rate limiting
46. CI/CD
47. Complex Issues
48. Today
49. Org IAM DX Platform SRE
50. Results • 5/11 teams doing R2s organically • > 5x more frequent deploys with < 10x duration • 80% critical services with tracing
51. Results (2) • 5 complex issues solved • > 99.99% reliability for User Management API • ~8ms -> ~3ms 99th perc latency for rate limits
52. Success
53. Vision Subject to change :) IAM DX Platform SRE PR SRE AR SRE AR SRE OX
54. Thanks @dschenkelman