To me it looks as if:
1- They dont have any idea how to really fix this.
2- The fix would be so time and work intensive the Execs have decided to do just some small fixes and wait till the number of players diminishes.
1 Like
Can you link it? Maybe i havent read the right one.
Ok In my 15 years as a bussiness Java developer I havent been in a project where a modification alogn with the “archeologic” code digging couldnt be estimated in a month time. Sure i can be wrong, but it looks weird to me. Im not talkign about rock solid estimates which dont exist lol but an aproximation. Is it a month or 2 months? What are the stages?
Here ya go. Ah yes, if you are talking just about estimating and forming some comprehensive plan - 1 month should be enough, I think.
Diablo II: Resurrected Outages: An explanation, how we’ve been working on it, and how we’re moving forward - General Discussion - Diablo 2 Resurrected Forums (blizzard.com)
Thank you. No idea why, but I have only read parts of this post before, not the full one.Ashamed to say i was a bit lazy and havent searched very hard. You are right they described pretty much what they are doing and it sounds good. I will scratch my ego by saying they even do what i loosely suggested lol
Breaking out critical pieces of functionality into smaller services:
Also
Right now we are writing code to change how we do this entirely, so we will almost never be saving to the global database, which will significantly reduce the load on that server, but that is an architecture redesign which will take some time to build, test, then implement.
Yeah so seems they are aiming to rewrite all the problematic stuff and fix it for good, which is good:). And obviously it takes time. So yeah the only stuff missing for me to feel as ok (or as ok as possible in this 40$ little f****p) is an approximate roadmap. I would be then willing to wait and not whine anymore, s**t happens, specially in software world.
2 Likes
Oh, you are not the only one 
Have you seen how many topics are here with claims like “just buy more servers!!” 
You mentioned that you’ve been working in this industry for 15 years… so no wonder you were suggesting microservices, so it is fine to scratch your ego in this case ) I wonder why Blizz didn’t pay enough attention to the scalability of their product.
1 Like
I think the top brass was seriously taken by surprise by the scale of the success
I dont think its the case here but interesting thing is the microservices, altough full of benefits, are not the remedy for all problems and can even sometimes degrade performance if used in a bad way ( you do actually add the comunication costs for all the pieces you split your apllication into). But its not the thread for such a discussion, and alsoi dont think its the case here, from the very few details we have heard. Just wanted to add as a curiosity , as the ultra hype for microservices starts to cool down, poeple as alwys start to notice the dark side, there is never a silver bullet:)
Can’t say that there is a “hype” around microservices now ) It was just a tool that hugely boosted the scalability of the software at some point so everyone got very excited and, as result, it was sometimes overused 
It’s like when “Agile” appeared in project management… I still have PTSD from that.
What is weird here - Blizz have the experience of building and maintaining MMO games, they should’ve been prepared to scope the db and communication layer changes properly, especially that they knew that they are moving to the new battlenet and there’ll be a spike in users.
1 Like