The number of baseball puns in this talk is off the charts.
(is there a baseball pun I should have used there? Idk I'm not a baseball person)
Last talk for today: "Reliability in the Big Leagues: How SRE Powers America’s Pastime" by Jessica Johnson and Chris Alexander, Major League Baseball.
Who can bypass these freezes? A bypass decision is based on "event type + service tiering + risk signals + resilience data (canary/staggered rollouts)"
They appear to have a set of automated tools that look at a variety of signals to determine if a change is safe to ship.
Very curious to know how they decide what tier each service belongs in. In my experience, everybody thinks their own service is tier 0.
What if we tuned our controls to the real impact for each service:
1. blast radius
2. impact to customers
3. acceptable risk tradeoffs
This lets us tune tiered responses to the actual level of risk.
Same problem occurs during every blanket freeze: people don't stop building, they just stop shipping. Changes pileup, risk builds, and critical patches that really ought to be pushed out are just sitting there.
Show of hands: "Who has been in a no-deploys-for-a-week code freeze before? Oh, all of you, excellent!"
drmorr