How does Site Reliability Engineering (SRE) approach production support? Why is it conditional, and how do error budgets try to avoid the inter-team conflicts of You Build It Ops Run It?
On Tech
How does Site Reliability Engineering (SRE) approach production support? Why is it conditional, and how do error budgets try to avoid the inter-team conflicts of You Build It Ops Run It?
Why is a hybrid of You Build It Ops Run It and You Build It You Run It doomed to fail at scale?
Why does Operations production support become less effective as Delivery teams and applications increase in scale?
Why do disparate Delivery and Operations teams result in long-term Discontinuous Delivery of inoperable applications?
What are the different options for production support in IT as a Cost Centre? How can deployment throughput and application reliability be improved in unison? Why is You Build It You Run It so effective for both Continuous Delivery and Operability?
How can You Build It You Run It At Scale be implemented? How can support costs be balanced with operational incentives, to ensure multiple teams can benefit from Continuous Delivery and operability at scale?
How can You Build It You Run It be applied to 10+ teams and applications without an overwhelming support cost? How can operability incentives be preserved for so many teams?
What is You Build It You Run It, and why does it have such a positive impact on operability? Why is it important to balance support cost effectiveness with operability incentives?
© 2021 Steve Smith
Theme by Anders Norén — Up ↑