Introduction to Site Reliability Engineering
Demystifying DevOps & SRE
· Virtual
In this session, we start with the basics of SRE, including some common terminology and theory, then dive into practical examples—including lessons learned from our own journey here at Datadog. We discuss the relationship between SRE and DevOps, what success looks like (and how to measure it), and how to identify and nurture both internal and external talent in order to build a cross-functional team. SRE is a large, complex topic, so the session ends with a live Q&A and deep-dive into some great topics.
Demystifying DevOps & SRE
Today’s topics 1. Clear up confusion about what DevOps and SRE are. 2. Discuss team and organizational structure. 3. Tips on finding and growing SRE talent. 4. Practical suggestions for incorporating SRE into your organization.
Today’s topics 1. Clear up confusion about what DevOps and SRE are. 2. Discuss team and organizational structure. 3. Tips on finding and growing SRE talent. 4. Practical suggestions for incorporating SRE into your organization.
DevOps: CAMS ● Culture ● Automation ● Measurement (or Metrics) ● Sharing
“The SRE Book”
Today’s topics 1. Clear up confusion about what DevOps and SRE are. 2. Discuss team and organizational structure. 3. Tips on finding and growing SRE talent. 4. Practical suggestions for incorporating SRE into your organization.
Organizing your organization ● Product Teams ● Squads ● Guilds
Squads
Guilds
DevOps is an idea; SRE is a practice. ● A cohort of of Site Reliability Engineers, organised and managed as a group, form an SRE team. ● SRE teams are versatile! ○ Code reviews, incident response, facilitate post-mortems ○ Supports a dedicated portfolio or a product team ○ Individual SREs may rotate in and out of products, sprints (though some might not)
Today’s topics 1. Clear up confusion about what DevOps and SRE are. 2. Discuss team and organizational structure. 3. Tips on finding and growing SRE talent. 4. Practical suggestions for incorporating SRE into your organization.
SREs have personalities ● Patience for staring at code ● Enjoy problem-solving ● Capacity for self-teaching ● Wide range of technical interests ● Great at communicating in different ways ● Big on teamwork and mutual trust ● Interested in mentoring / teaching
SREs have backgrounds ● Traditional “ops” or “dev” profiles ● Customer success agent ● PhD in computer science ● Dropped out of high school Great SRE talent can come from anywhere!
Today’s topics 1. Clear up confusion about what DevOps and SRE are. 2. Discuss team and organizational structure. 3. Tips on finding and growing SRE talent. 4. Practical suggestions for incorporating SRE into your organization.
SRE: Standalone team? Embedded resource? ● Depends on your organization; on your realities. ● Try a few different things—see what works! ● This is where the CAMS acronym comes into play. ○ Culture ○ Automation ○ Measurement ○ Sharing
Pitfall(s)
Today’s topics, reprised 1. Clear up confusion about what DevOps and SRE are. 2. Discuss team and organizational structure. 3. Tips on finding and growing SRE talent. 4. Practical suggestions for incorporating SRE into your organization.
Demystifying DevOps & SRE Fin.