I have to say, I went through the same thing. I originally saw my costs go up about 8x with the new pricing, so I posted that I was going to look into other options. I did, and they seemed comparable, but transferring the database was going to be a cost problem. Then we got the news that the instance pricing reporting was broken, and the free quotas went up. I experimented with instances and the new quotas, and found that with these changes (and correct usage reporting), with the new pricing my costs will stay flat.
I do totally love Google App Engine, and I was seriously bummed about moving -- I'm glad I'll be able to stay, and relieved that the initial scare proved to be exaggerated. We're heading into launch soon, and we'll see how the numbers change, but I'm much less worried about it than I was. I just started a project for a low-traffic site for a corporation, and recommended GAE/HR with no real worries. The only thing I'd ask for is better M/S datastore support. :) It meets our needs really well, other than the outages.... -- Rachel On Thu, Sep 15, 2011 at 7:21 PM, Chapman Howser <[email protected]>wrote: > You're not the first to make these points. > > Unfortunately I don't think they are widely understood. > > And for that reason GAE may be fatally wounded from the recent poorly > informed outrage. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
