When achieving competitive pricing demands customers can understand and apply a secret sauce, something is seriously lacking. Although I like GAE, it needs a lot of work on non-technical, whole-product solution elements. stevep
On Jan 8, 12:30 am, "Brandon Wirtz" <[email protected]> wrote: > I can name that tune in a LOT less money. We are actually looking at > building a twitter-esque service on GAE. (actually doing Video with Text and > Audio) and we are estimating that we can push Video,Audio and Text at a > price of .32 cents a gig delivered regard less of number of follows or > followers. Our biggest concern is the 12 cents each way on the bandwidth > more than just about anything else. > > We did the math on things, and the biggest limitation is the size of the > memcache, which doesn't scale with the number of instances or the size of > the instances. But we even solved most of that issue. (sorry not sharing > how). > > But in all the conversations about price it always comes down to things are > expensive if you do things the way you are used to doing them rather than > doing them the way GAE is optimized to do them. My biggest complaint with > pricing is that what costs money has shifted more than once. Which cause use > to "re-optimize". I realize that I exploit the pricing to get the best > price... but as with all pricing you have to lose money on one or to savvy > guys to make up for the not so savvy guys you take to the cleaners :-) > > > > > > > > -----Original Message----- > From: [email protected] > > [mailto:[email protected]] On Behalf Of jon > Sent: Sunday, January 08, 2012 12:13 AM > To: Google App Engine > Subject: [google-appengine] Re: vijayp on migration of partychat from GAE to > EC2/GAE-hybrid; from $20/day expense to < $1/day > > Ikai, sure Google has chosen to differentiate on advanced features, not > price. It's OK to charge a little more than your competitors. The question > is, how do you know if you're now charging correctly? Are you charging too > much? Are you charging too little? How do you know? > > Based on user feedback, I'd say you've charged too much. I don't mind most > of the price increases, but the datastore operations are very expensive. > It's so expensive that the Relation Index Entity technique proposed by your > own Brett Slatkin has become cost prohibitive. If Twitter was built on GAE > using Relation Index Entity, each tweet made by a popular user with 1 > million followers would cost $1 each. Let's say there are 1000 such users on > Twitter. And if each one tweeted 10 times a day, the cost would be $10,000 > a day! > > I mean c'mon, Google must be seriously overcharging when best > practices/solutions suggested by Googlers themselves have become unusable. > > On Jan 7, 7:20 am, "Ikai Lan (Google)" <[email protected]> wrote: > > Andrin, that's a totally fair argument, and one that we are always > > talking about. I think there are ways we can make GAE can provide > > value, but the key is for us to think about value, not price. If we > > obsess about price per megabyte of bandwidth, we're losing sight of > > our goal of enabling developers. We need to demonstrate that the total > > cost of ownership of GAE is top notch by continuing to execute and improve > the overall platform. > > > -- > > Ikai Lan > > Developer Programs Engineer, Google App Engine plus.ikailan.com | > > twitter.com/ikai > > > On Fri, Jan 6, 2012 at 4:34 AM, Andrin von Rechenberg > <[email protected]>wrote: > > > > One other interesting thought is that people often justify the > > > higher price with the stability of GAE and that Google takes care of > > > running your system and you dont have to carry a pager. > > > The flaw with this justification is, that if my app would cost > > > $50'000 a month on AppEngine and $20'000 somewhere else, I would run > > > it somewhere else! > > > For the extra $30'000 i would save, i could hire 2 really great Site > > > Reliability Engineers that take care of running the system and make > > > the experience for my developers just as good as GAE's. Many people > > > have made systems scale outside of AppEngine, which is for an > > > experienced engineer as hard as adopting to GAEs limitations. So I'm > > > wondering who Google targets at the moment with AppEngine. For > > > people that really think big, GAE might not be the choice anymore. > > > And Amazon is really taking the market these days. > > > > I truly hope that one day GAE is so competitive that it takes the > > > market as much as EC2 is taking it now. From my point of view, the > > > pricing changes were a huge set back (maybe it was a success for > > > Google's Business side), but I'm positive that sometime in the > > > future GAE will become more competitive again. > > > > Cheers, > > > A big GAE-Lover > > > > On Fri, Jan 6, 2012 at 12:57 PM, Leandro Rezende < > > > [email protected]> wrote: > > > >> run as u can =P > > > >> 2012/1/5 Shane Elbo <[email protected]> > > > >>> I've just started to learn about GAE. Should I go for this > > >>> strategy instead of full rely on GAE? > > > >>> -- > > >>> You received this message because you are subscribed to the Google > > >>>Groups "Google App Engine" group. > > >>> To view this discussion on the web visit > > >>>https://groups.google.com/d/msg/google-appengine/-/f0eK3bnZZJYJ. > > > >>> 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. > > > > -- > > > 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 > athttp://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.
