2 ms·

I'm not sure how you would even distinguish it from never being open. I tried to sign up at 7:01 and it said, "Registration closed." I reloaded 5 times and at o

I'm not sure how you would even distinguish it from never being open. I tried to sign up at 7:01 and it said, "Registration closed." I reloaded 5 times and at one point saw the form but clicking through lead to the first 500 I've ever seen from Google. How can they not scale this? This is 3rd-year-in-college 2 week project level scaling challenges.

chinpokomon 14y ago
It's an interesting problem... before virtual servers. The traffic spike Google receives for events and Nexus device launches must look like a DOS attack. We don't know where the bottleneck lies, but considering the 500 server error I received on my first spin of the wheel, I don't think it was a network problem. I wonder if the load balancers are effectively distributing things? Since it seems that so many people got dropped at transfer points, maybe they just need an improved queuing system so they can process requests without putting strain on registration systems or Google Wallet? Maybe they should rewrite this system with Go? Then they could reduce the number of servers they use from 30 down to 2? :-)