2 ms·

Clearly as demonstrated by this mess. What is your point exactly? They are doing it wrong, however they are doing it. OP suggested they use AWS (which alone as

Clearly as demonstrated by this mess. What is your point exactly? They are doing it wrong, however they are doing it. OP suggested they use AWS (which alone as stated doesn't solve the problem). Then first commenter said they are using AWS. I simply quiped ~ "more like misusing". Where in there is something wrong? Unless 30+ minute wait times is good design?

nemothekid 14y ago
"Misusing" is wrong as well because no one is aware if they aren't doing things by the book. This isn't the first time a company has launched an MMO only to have it crash multiple times at launch. Starcraft had similar problems, and Blizzard STILL didn't get it right when it came time to launch Diablo. Trivializing Diablo's issues to "well Blizzard should have used AWS instead of managing their own servers" is just wrong, and doesn't get anyone anywhere. Its clear launching MMO's is hard. I'm not even sure the author is an authoritative figure on the subject - his service most likely grew slowly over months, rather than a million people at once. EA's issue could be completely unrelated to the fact they used AWS or not (or if they implemented DRM or not). Again, games crashing at launch isn't a new phenomenon. AWS allows you simply add and remove machines. If EA has 100 machines at this point, there is nothing AWS can do. It may even be possible their AWS infrastructure is on point and the problem relies elsewhere. In any case, we will never know if people just quip "well they should have used AWS/Postgres/MongoDB"