News for hackers. Stuff that matters.
Re:Mapvelopes by reso on Tuesday November 29, 2011 @04:00PM (#3292150)
AppEngine is great, until you get HN scale traffic. The user should have been prepared.
Re:Mapvelopes by ericd on Tuesday November 29, 2011 @04:43PM (#3292329)
Traffic from an HN link is a lot over the course of a few hours, but it isn't that hard to handle. A single dedicated server usually won't even break a sweat. That's why this looks really bad.
Re:Mapvelopes by stickfigure on Tuesday November 29, 2011 @07:02PM (#3292954)
What do you want for free? "A single dedicated server" costs something... this guy is almost certainly running on the free quota.

I don't think this looks bad for Google -- it looks bad for the author. The fact that he's using the freebie *.appspot.com rather than a dedicated domain gives you some indication of his dedication to the project.

Re:Mapvelopes by ericd on Wednesday November 30, 2011 @06:13PM (#3297331)
A single server not breaking a sweat means that this can be handled by a middling VPS that is breaking a sweat, and that load only lasts a few hours. That means that it's stupidly cheap for Google to provide for a few hours of load like this, and the ability to absorb a huge spike on a cheapo plan is supposed to be one of the main points of cloud hosting.

Lots of people make cool stuff without dotting all the i's. That doesn't look bad on them - it just means they're doing the hard stuff and skipping the grungy parts of a project until it seems necessary.

Re:Mapvelopes by thisisblurry on Tuesday November 29, 2011 @04:05PM (#3292170)
Who's to say that the user posted the link on their own?
Re:Mapvelopes by jordan0day on Tuesday November 29, 2011 @04:13PM (#3292197)
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.

Re:Mapvelopes by azylman on Tuesday November 29, 2011 @06:55PM (#3292936)
You 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.

Re:Mapvelopes by groby_b on Tuesday November 29, 2011 @07:18PM (#3293011)
To 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.

Re:Mapvelopes by azylman on Tuesday November 29, 2011 @07:46PM (#3293100)
Yeah, 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.