GitHub says the recent outages weren’t just bad luck, but a mix of rapid growth, tight architectural coupling, and systems that couldn’t cope with the load.
“Tight architectural coupling” made me think of your “main corridors” line — like there’s one hallway everyone has to use and when it gets crowded, the whole building feels broken. When GitHub says coupling, do they mean shared state (like one database/queue everyone leans on) or do they mean long synchronous call chains where one slow dependency drags everything down? not sure about this one.
