Again, I love appengine and I love what google engineers are doing with it. They are amazingly skilled people and are improving the platform as fast as they can.
The only thing you can't tell me is that it's a good deal pricing wise. The pricing is just disturbing if you want to do something at scale. Our company was bootstrapping for two years and we were forced to raise capital in order to pay appengine bills. Of course we could flood our users with ads, but that's not what we are passionate about. -- timh, People like me have started with appengine because the requirements and pricing was right at the time. As you might know, requirements and pricing changes through time and server migration can kill companies. Kaan, My service is the typical >1mm subscribers social network. The $$ is spent mostly in read and writes and output bandwidth. It's definitely more expensive and complex than snapchat. Immediate hacks snapchat must to do in order to stay below $100k a month in server costs: - keep a pool of at least 20 "resident" instances. (they become SO idle that become zombines and never respond anymore, but you're paying expensively for it) - move the output bandwidth to a cheaper CDN. moving my image serving to maxcdn has reduced my output bandwidth costs from $2000 a month to $300. - Snapchat probably doesn't need this, but twitter/facebook would definitively need: separate the push notification service in other module and then keep a pool of at least 10 resident instances again. this would be necessary to reduce spike effect (instances booting like crazy) with the britney spears tweets. thanks rafa On Tue, Jan 21, 2014 at 3:52 AM, timh <[email protected]> wrote: > Just for the record, the app I was talking about might only have 2000 > users, but it is by no means a simple application. > > I has approximateley 30 different models. Fully defined with RBAC > security model scoped down to parts of models. > reporting, audit trail records for every change to data, (when and what > was changed, by who), etc.... > > The entire system is modeled in UML, python models, views, URL paths, > security declarations, form schemas all directly generated from the model. > What elements of a view appear for the combination of user, context, and > view control page layout, so the application is intensely dynamic and most > cached data's scope is only effective for a single user. > > So even complex applications can be run in a cost effective manner on > appengine. > > But no point trying to stick a square peg in a round whole. If you data > model, or processing requirements don't suit appengine and you can't start > instances quickly then > you may well be on the wrong platform. > > Now more than my 2c worth ;-) > > T > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/google-appengine. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
