“[SRE is] what happens when you ask a software engineer to design an operations function.”
This is how Ben Treynor Sloss, VP of Engineering at Google, defined SRE when he coined the term in 2003. But what are the core responsibilities, habits, and tools of an SRE today? How can you embrace these practices on your own team?
Whether you’re still figuring out how to create a site reliability practice at your company or trying to improve the processes and habits of an existing SRE team – the more you know, the better. Our SRE Handbook shares the philosophies, habits, and tools of successful SREs, exploring topics like:
- What makes an SRE successful?
- SRE tools and processes
- Setting your SREs up for success