The visual summary below is based on a post by Will Larson, who started the SRE function at Uber. His post elaborates on a “trunks and branches” model for developing infrastructure-facing teams.
It also covered an interesting perspective on the balancing act of budget and service quality. I will explain the visual summary underneath it.
An explanation of the above visual summary
- Long-term cloud infrastructure success depends on balancing both elements of high Service Quality and a reasonable Investment Budget
- Service Quality can get torpedoed by morale busters like non-stop grunt work, not enough engineers, etc.
- Investment budget can get torpedoed by continuously high cloud costs and an excess of branch teams working on problems that aren’t solving immediate problems
- The key is to always keep an eye on these “busters” that can torpedo your long-term return on cloud investment
⬇️ Seems like you’re finding this article useful 🥳
Join our newsletter to get more insights like this in the future ⬇️
Founder at SREpath
Ash actively champions the expansion of Site Reliability Engineering as a software operations practice. His goal is to support the implementation of SRE practices and encourage ongoing team development. Before starting SREpath, Ash worked as Director of Operations at a diversified organization, overseeing a team of teams for over 12 years.
Latest posts by Ash Patel (see all)
- #17 Lessons from SRE’s Wild West Days (with Rick Boone) - November 29, 2023
- #16 Journey to Cloud Infrastructure Leadership (with Sreejith Chelanchery) - November 29, 2023
- #15 Growing Reliability Engineering Across 5+ Companies (with Nash Seshan) - November 14, 2023
