Chicago, IL
2017-11-03
Description
Designing distributed systems means considering failure scenarios—both likely and less so. Will the network let you down? (Almost assuredly.) Will some portion of your IaaS misbehave? (Have you met computers?) We build in graceful degradation for much of our automation but often neglect the (just-as-essential) human interactions.
The classic “hard problems” of cache invalidation and naming things revolve around our understanding of what’s correct and true and our agreements with one another on scope and relevance. Communication is essential for making context-dependent decisions.
Whether we’re attempting to determine the current state of reality or distinguish logical boundaries, democratized observability is key to answering our questions. As the fractal complexity of our distributed systems grows, we need to mindfully choose practices that work with our tooling. You can’t buy a silver bullet, but you can forge one from the collaborative efforts of your team.
Slides
Tweets
Time to talk #devops with @bridgetkromhout #MVPBuzz #mvpcc pic.twitter.com/BdOlIqswWb
— Duane Newman (@duanenewman) November 3, 2017
Listening to @BridgetKromhout help us understand the importance of empathy in DevOps as well as about 100 other fantastic tidbits of wisdom pic.twitter.com/mZyD22GkD9
— Doug Hemminger (@DougHemminger) November 3, 2017
@bridgetkromhout talking about “the DevOps” @MVPAward #MVPBuzz. pic.twitter.com/EqUVbBuNVf
— David Pine (@davidpine7) November 3, 2017
"If you used a credit card today, you interacted with a mainframe. Congratulations." - @bridgetkromhout #MVPBuzz
— Eric Potter (@pottereric) November 3, 2017