According to Asobo, this issue was caused by a cache that was overloaded and constantly restarting. This was used in part of the authentication process, I believe when they check what content you have. This explains why people had missing content if they were lucky enough to get in. This was my experience - got in after a very long load time and then couldn’t really do anything due to missing content.
This doesn’t seem like it’s a Microsoft cloud issue per se, it seems like Asobo had a single point of failure in the design that didn’t scale well. Today seems like the CDN limits are finally being reached, as it took a while to load up new areas. Getting into the game was no issue, though.
halcyoncmdr@lemmy.world 1 year ago
I’d say it’s more on how the developers setup their system to utilize (or not utilize) those dynamic capabilities.
The game devs not taking advantage of that properly should be on them. Put the blame where it belongs.Don’t let the devs off the hook just because you want to at least partially blame the MS cloud. Microsoft’s systems CAN handle dynamic loads when setup properly, we see it all the time.