SRE

SREs are responsible for the “availability, latency, performance, efficiency, change management, monitoring, emergency response and capacity planning of their service(s).”

They use service-level objectives (SLOs) and error budgets to set shared expectations for performance and balance reliability with innovation, respectively.

SRE is all about applying a software engineering mindset to system administration. As a software engineer, you look at the business requirements and develop the system. Likewise, a Service Reliability Engineer needs to look at how each disruption can affect the business requirement and then find a solution for it accordingly.

“https://docs.google.com/presentation/d/1qcQ6alG_qUg3qWf733ZsDnTggwzqe4PZICrFXZ1zQZs/edit#slide=id.g75945b48fe_0_117”

“https://youtu.be/GnvXfFcfEPg?si=g7jeyaYk0pn5iYBo”

“https://static.googleusercontent.com/media/sre.google/en/static/pdf/art-of-slos-handbook-a4.pdf” sre book {% endembed

“https://www.youtube.com/playlist?list=PLIivdWyY5sqJrKl7D2u-gmis8h9K66qoj”

“https://sre.google/resources/practices-and-processes/twenty-years-of-sre-lessons-learned/”