{"id":280,"date":"2021-08-31T14:40:23","date_gmt":"2021-08-31T14:40:23","guid":{"rendered":"https:\/\/fde.cat\/?p=280"},"modified":"2021-08-31T14:40:23","modified_gmt":"2021-08-31T14:40:23","slug":"sre-weekly-issue-260","status":"publish","type":"post","link":"https:\/\/fde.cat\/index.php\/2021\/08\/31\/sre-weekly-issue-260\/","title":{"rendered":"SRE Weekly Issue #260"},"content":{"rendered":"

View on sreweekly.com<\/a><\/p>\n

\n

A message from our sponsor, StackHawk:<\/h2>\n

Check out this guide to modern dynamic application security testing to learn how it works and what to look for in tooling.
\nhttp:\/\/sthwk.com\/dynamic-appsec-overview<\/a><\/p>\n<\/div>\n

Articles<\/h2>\n
\n
[Increment: Reliability] Interview: Dr. David D. Woods<\/a><\/div>\n
\n

People throw around \u201cresiliency\u201d quite often when they mean \u201creliability\u201d or \u201chigh availability\u201d. Dr. Woods sets the record straight.<\/p>\n

Ipsita Agarwal \u2014 Increment<\/small><\/p>\n<\/div>\n<\/div>\n

\n
[Increment: Reliability] The process: Implementing Yelp\u2019s failover strategy<\/a><\/div>\n
\n

A key part of their strategy is to keep their service running at 50% capacity or less, allowing them to lose a datacenter without overloading the remaining datacenter.<\/p>\n

Mathieu Frappier, Dorothy Jung, and Qui Nguyen \u2014 Increment<\/small><\/p>\n<\/div>\n<\/div>\n

\n
[Increment: Reliability] On adaptive capacity in incident response<\/a><\/div>\n
\n

In issue #236<\/a>, I linked to an excellent paper by Dr. Richard Cook and Beth Long about engineering resilience in incident response. Now they\u2019re back, teaming up with John Allspaw to summarize and expand on that paper!<\/p>\n

John Allspaw, Beth Adele Long, and Dr. Richard Cook \u2014 Increment<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Security Chaos Engineering: How to Security Differently<\/a><\/div>\n
\n

A quick s\/security\/reliability\/g<\/code> and this is an SRE article; the same principles apply to both fields.<\/p>\n

Aaron Rinehart \u2014 Verica<\/small><\/p>\n<\/div>\n<\/div>\n

\n
SRE2AUX: How Flight Controllers were the first SREs<\/a><\/div>\n
\n

How can we apply the tenets and principles of NASA mission controllers to our SRE work?<\/p>\n

Geoff White \u2014 Blameless<\/small><\/p>\n<\/div>\n<\/div>\n

\n
SRE as Organizational Transformation: Lessons from Activist Organizers<\/a><\/div>\n
\n

Genius idea: we can take our lead from activists as we try to win over our organization to adopt SRE principles.<\/p>\n

Chris Hendrix \u2014 Blameless<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Atlas: Our journey from a Python monolith to a managed platform<\/a><\/div>\n
\n

This insightful observation caught my eye:<\/p>\n

\n

It\u2019s unnecessary overhead for a product team to plan capacity, set up good alerts and multihoming (automatically running in multiple data centers) for small, simple functionality.<\/p>\n<\/blockquote>\n

Naphat Sanguansin and Utsav Shah \u2014 Dropbox<\/small><\/p>\n<\/div>\n<\/div>\n

Outages<\/h2>\n