Same for me -- my main app (which is still in the testing and demoing phase) is going from $.31/day (which was already too high for the very occasional usage) to ~$2.50/day, and that's before it even has any users -- the unpredictability of the costs on launch is a big problem. It's in Java, and all the costs are frontend instance costs. I'm in the process of setting up my first AWS account. I've been recommending GAE to everyone and using it for my apps for the last couple of years, but I'm going to have to do some serious cost comparison before investing any more time or money in it.
I like GAE a lot, otherwise -- please, Google guys, reconsider and make this more affordable? -- Rachel On Thu, Sep 1, 2011 at 6:01 AM, Pieter Coucke <pieter.cou...@onthoo.com>wrote: > I know that 20 cents a day is peanuts, but an increase from $ 0.2 to $ 8 a > day for my app is just too high. > > My app consists of bursts of messages in the queue that I want to be > processed as fast as possible. I could just set the rate to 100/s and never > look back at it. Now I need to disable my queue concurrency to avoid many > instances running. > > Like others in this thread, I thought the new billing wouldn't be as bad as > expected. I'm now trying java multi-threading again (hoping this issue is > magically fixed: > http://code.google.com/p/googleappengine/issues/detail?id=4834) and see if > that helps (I still see 5 instances running now). > > I use Java and moved from EC2 to App Engine so I wouldn't have to worry > about peaks and adding more servers (that was before Elastic Load Balancing > and Autoscaling was introduced). Also, I didn't want to bother with OS > updates but want to focus on what I'm good at (development). I'm willing to > pay more for that ease of mind. For me the strong point of App Engine is > the ease of deploying/upgrading my apps. EC2 provides better flexibility > for controlling scaling, cdn, messaging and even a scalable simpledb, but at > a much higher operational cost for me. It's easier as a developer when the > App Engine team has already decided for me on which platform, database, > memcache, queue, ... to use. The learning curve was sometimes steep > (transactions for entities with different parents) but I'll try to remember > this as a good way of learning to create scalable sites. > > The strong point of app engine (I didn't have to care about the number of > servers which makes it a real cloud solution) has gone with the new pricing. > EC2 micro instances are just $ 0.02 and give me 613 MB. I already > refactored my site for App Engine so each server can die at any moment, so > why wouldn't I go to EC2 (simpledb, elasticache) now? > > One of my clients asked me to create a (big) site on App Engine based on my > advocacy, I will probably need to rethink that decision. > > Sorry for the hard work of the App Engine team, but I'm really disappointed > here. > > (and apologies for the not so short answer) > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
