Let me correct myself. It would have been trivial if they would have designed new accessibility/database code from the outset. This is all front end stuff. It’s true, that fixing it in a live environment is now an order of magnitude or more complex, with lots of opportunities for catastrophic results.
This is why you need to plan and scope these kinds of capacity issues from the beginning.
The fact that it obviously wasn’t, tells me a lot about the team’s priorities. From seeing Dave B’s video on twitter suggest there really work resources available, but, to quote D3’s lead Mr. Wilson, “Dave B, that f*****…”
So, I suppose current Blizz must have a similar respect for the potential of those resources.
Going with a single global domain was such a huge change they should have anticipated that the old DBM code would not scale up.
Amen, Sister!! Preach on! I feel entirely the same way. But, I will admit, when it works, I love it. My problem is that it’s not working enough. I’m in my 6th queue of the morning, waiting over 3 hours today. A TUESDAY.
This is something I have to remind myself of. I worked in provisioning global IT real-time solutions for more decades that I feel comfortable admitting, and I can recall dozens of times I and my team could have implemented some truly impressive, elegant solutions, if only we could have squeezed a few more pennies out of management. Most of these works of art never got off the drawing board.
Or the cocktail napkin in some cases…