3 ms·
Ha ha ha. Good one, reso. What? You're serious? We should all design massive scaling and redundancy features into our hobby projects? That's absurd. It's not
by jordan0day 15y ago
Ha ha ha. Good one, reso.
What? You're serious? We should all design massive scaling and redundancy features into our hobby projects? That's absurd.
It's not like Google can't handle the extra bandwidth, it'd be much better if they left the page up and reached out to the developer to upgrade their account.
- azylman 15y agoYou don't need to "design massive scaling and redundancy features into hobby projects" to be prepared for high bandwidth in App Engine. You basically just need to check the box to tell App Engine to charge you when you go over quota instead of shutting down your site... This doesn't happen from any "fault" of App Engine's. They're using a free, limited account and couldn't handle all the traffic they received.
- groby_b 15y agoTo be fair to the author, it can be surprising how much traffic you get, especially if it's your first foray into "web stuff". I recently posted a presentation of mine and was completely blindsided by how quickly I burned through the available quota. Granted, it was showcasing WebGL and WebAudio, so there was a bunch of data per download, but I still only barely managed to put in CC info before I reached quota. (And the best part, traffic fell off as soon as I signed up for billing. :) It'd be nice if users could indeed bump quota, as suggested above.
- azylman 15y agoYeah, I didn't mean to imply that it was the author's fault, I was just flabbergasted by the assertion that it was a lot of work to make a GAE application scalable. Really, it's only the author's fault if he posted this link. I did like the idea of user's bumping quota, as well.