The world moved on from 1 server 1 realm long ago. A given hardware server may serve multiple realms, or half a realm shared with another hardware server.
It doesn’t work like that any more…
1 Like
There was never 1 server = one realm in wows history.
The cloud tech is great in theory, but has proven very lack-luster in practice, Which is why they need to remove classic from their layering.
![:man_facepalming:](https://d38bqls1q93fod.cloudfront.net/en/wow/images/emoji/twitter/man_facepalming.png?v=6" ":man_facepalming:")
You really should go and secure investment for your own game. Clearly you have ideas far and away better than everyone else, which is why no-one is using them.
/endsarcasm
Dude… you are right… and also wrong at the same time…
Hardware is important…
But servers are not static anymore… that would be a total waste of hardware AND money paying for said hardware…
The ONLY time it is going to operate at anything close to 99% capacity is during the launch… Even then the contract that Blizzard has with the data centers (I think they are all still run by AT&T yes) Will provide for short term temporary overflow as part of the SLA…
Vanilla wow didn’t use the cloud technology and it was a cohesive world using blades as realms, worked just fine, not need for layering or sharding…
2 Likes
No, I am not and I never have. That was you trying to be clever with a dis that failed.
You have things backward, however. Hardware is not PLUGGED into any server. NetOps takes care of hardware allocation and in their cluster. Realms are spun up, hell, individual instances, 5mans, and raids, spin up as needed.
I do not think they are using containers but I would not put it past them either.
Like I said before, your understanding of the under arching network and hardware system with dynamic resources is very limited and shows why you are so misinformed about layering
I’m not ignoring it at all, actually. It’s the entire basis for my argument. The fact the population will dive means you don’t have to do anything to deal with the queues, because the problem will solve itself once the tourists are gone.
Assuming the population spreads evenly across all realms (which never happens). If queue times are still “too high” (subjective) after the tourists are gone, they can just add realms to deal with the population.
What happens when they remove layering and the servers have massive queues because not as many people quit as they expected? Same thing. They add more realms.
At least with my way, we actually get vanilla like we wanted.
1 Like
It would be worth it, to maintain a cohesive world, otherwise they just aren’t going to do it. We could have dedicated server blades per realms, they just don’t want to do it, which is why layering or sharding are the only options they are presenting.
OMG. . just . .
Containers for Instances, BGs, Raids, World is my assumption.
Mine too.
You got me scratching my head on AT&T also. I wonder if they are still sub contracting with them or if they have converted to AWS. Hrm
1 Like
Your experience of Vanilla stability and mine, don’t match up. Also, that’s never going to happen because Blizzard’s modern infrastructure doesn’t work like that.
THE PATH FORWARD: SECOND PROTOTYPE
Speaking of engineering, World of Warcraft is a very data-driven game, which means the basic code is flexible and the specific way it behaves is controlled by information contained in databases. Things like quests, monsters, items, and the rules for how these all interact are defined by the designers and artists in data.
So we asked ourselves, would it still be possible to deliver an authentic classic experience if we took our modern code, with all its back-end improvements and changes, and used it to process the Patch 1.12 game data? While that might seem counterintuitive, this would inherently include classic systems like skill ranks, old quests and terrain, talents, and so on, while later features like Transmog and Achievements would effectively not exist because they were entirely absent from the data. After weeks of R&D, experimentation, and prototyping, we were confident we could deliver the classic WoW content and gameplay without sacrificing the literally millions of hours put in to back-end development over the past 13 years.
While our initial effort helped us determine the experience we wanted to provide, this second prototype really defined how we’d get there. Starting from a modern architecture—with all its security and stability changes—means the team’s efforts can be focused on pursuing an authentic classic experience. Any differences in behavior between our development builds and the patch 1.12 reference can be systematically cataloged and corrected, while still operating from a foundation that’s stable and secure.
1 Like
Now I know one of two things…
you are an idiot who thinks he knows about things so much so that you lie to yourself about your own level of knowledge
Or you are just trolling…
I am at a 80/20 split here…
2 Likes
Like I said way up in the thread.
Servers come from unicorn farts right?
1 Like
I watched a dude pull out a blade from a server and said this is Tichondrius, one of our more popular realms, so what are you talking about?
That was YEARS ago!!
You’ve managed to describe the problem while ignoring the scale.
Your queues with no layering and queues with layering, are not the same thing. By an order of magnitude.
Less than 2 years ago it was uploaded.
This story mentions 27 data centers… but not who owns them… Prob still with AT&T… I STILL cant include links… WhaaatTF
https:// news.blizzard. com/en-us/blizzard/21700686/life-at-blizzard-global-network-operations-center-gnoc
1 Like