News for hackers. Stuff that matters.
Re:Google App Engine team answering about New Pricing (ongoi... by ultrasaurus on Wednesday May 18, 2011 @02:43PM (#2561192)
Yes that was my understanding. I was using a simple GAE app to serve some of the static content for some sites (GAE is a favourite tool in my toolbox). It was fast and I rarely went over 1gb/day but when I did it would only cost a few cents.

I expect that is exactly the kind of application that they want to dissuade with this change.

Re:Google App Engine team answering about New Pricing (ongoi... by detst on Wednesday May 18, 2011 @05:06PM (#2561821)
Care to elaborate a little about how well static content works for you?

I'm working on something where I was thinking about using S3 for static and building a really simple GAE datastore-backed JSON API pulled in from the static files.

Nothing complex but I want it to perform as well as possible. If GAE would work just as well, I'm thinking I should just keep everything there.

Do the front-end cache servers prevent unnecessary hits on the app server instances?