Centralization

The potential for noticeable, widespread outages is an unappreciated component of centralization. I started using Exchange in 2000 as a tier 3 sys admin at a Fortune 500 company. Big company everyone’s heard of, but you wouldn’t hear about it when our email system went down for a day. If you were actively looking at buying from us, you might get a call from your sales guy letting you know he’s going to need a little extra time on a quote. Or you might get the email from an “odd” address (the sales guy’s gmail account or whatever). But it wouldn’t be national news. It wouldn’t be anything that everyone knew about.

I worked a major outage every couple of years from 2000 through 2015 when we moved to the hosted Exchange service. I sat next to the network infrastructure team. They’d have site outages that impacted a single office with a couple hundred people working there. Inside the company, even that wasn’t general knowledge. Every couple of years, they’d have something massive melt down. Someone would have an upgrade go sideways and a quick three hour task turned into a full weekend with dozens of people working on restoring service. Even cyber attacks. Worked at a place that’s been hacked. It made the news, but like “third page, under the fold” kind of news.

Fundamentally, there isn’t anything different going on today. It’s just that we don’t have ten thousand companies with ten thousand email systems, ten thousand authentication directories, ten thousand file servers, ten thousand networks. We have ten thousand companies of which at least 8,000 of them have all their stuff in Google, Microsoft, or Amazon. Something goes down, you notice. That’s true of email systems, authentication systems (federated auth, if you “log in with Google!” to all of your favorite sites, you lose access to those sites when Google’s auth framework goes wonky), networks, etc.

Leave a Reply

Your email address will not be published. Required fields are marked *