Saving Someone’s Day

When Google AppEngine launched it was match made in heaven between developer/entrepreneurs + launch of their dream startup/project. It is true up to certain extent no doubt about that. Apart from being a great platform for developers to jump start their idea which took them weeks if not months before, It is not considering apps like Twisternow for rapid scalability in terms of request/user/bandwidth quota. 

Absorb spikes in traffic. When a web app surges in popularity, the sudden increase in traffic can be overwhelming for applications of all sizes, from startups to large companies that find themselves rearchitecting their databases and entire systems several times a year. With automatic replication and load balancing, Google App Engine makes it easier to scale from one user to one million by taking advantage of Bigtable and other components of Google’s scalable infrastructure.

• They wrote a code (in python), deployed on AppEngine - Great!
• They get to have their own domain instead of twisternow.appengine.com - Great !
• People started noticing their app and liked the simple idea of Twisternow - Super great!
• More and more people come to your site - Super super great!
• Then what ? - Over quota from AppEngine - Not so great!.

So for Twisternow guys all they got is initial ramp up , but as the message says they are probably moving their boxes somewhere else. It would be good to see if Google AppEngine can have few intelligent rules built in based on applications popularity/page views they toggle the quota, probably have app owners pay some money to scale smoothly without hitting against the quota wall. I'm sure that will be a preferred option for application owners, rather than thinking of 

• new infrastructure 
• time associated with the move 
• The most important - Impact of user mind share shifting somewhere else. As this is a key factor always for new startups, competitors launch every minute.

Blogged with MessageDance using Gmail | Reply On Twitter