Skip to content
rule 11 reader
  • about
    • about me
    • mailing list
    • author page
    • rss feeds
  • reading
    • technology books
    • skills books
    • fiction books
    • philosophy & culture books
    • christian books
    • papers
    • worth reading
  • categories
    • career
      • career
      • design skills
      • communication skills
      • education
      • soft skills
      • troubleshooting skills
    • coding
    • complexity
    • culture
    • ddos
    • ipv6
    • other technologies
    • research
    • reviews
    • routing
      • bgp
      • bgp security
      • eigrp
      • is-is
      • ospf
      • mpls
      • other routing
    • security
    • standards
    • worth reading
    • content type
      • long video
      • long audio
      • short video
      • written
    • other
      • governance
      • humor
    • archive
  • the hedge
  • history
  • resources
    • my goodreads
    • my feedly
    • network icons
  • photos

On the ‘net: Crashes and Complexity

It’s a familiar story by now: on the 8th of August, 2016, Delta lost power to its Atlanta data center, causing the entire data center to fail. Thousands of flights were cancelled, many more delayed, and tens of thousands of travellers stranded. What’s so unusual about this event is in the larger scheme of network engineering, it’s not that unusual. If I think back to my time on the Escalation Team at a large vendor, I can think of hundreds of situations like this. And among all those events, there is one point in common: it takes longer to boot the system than it does to fix the initial problem. —CircleID

Related

Posted in COMPLEXITY, ON THE NET
← snaproute Go BGP Code Dive (8): Moving to OpenSelf-Improvement Through Time Travel →
© 2023 rule 11 reader | Powered by Beaver Builder
Scroll To Top