The email sent will contain a link to this article, the article title, and an article excerpt (if available). For security reasons, your IP address will also be included in the sent email.
Hey, it's HighScalability time:
- The Herokulypse. A cautionary tale of what can happen when scalability is left for later. Rap Genius created quite a stir (reddit, Hacker News) when they documented high costs ($20K/month for 15 million monthly uniques) and poor performance (6 second average response times) using Heroku's random routing mesh. The cause was tracked to queuing at the dyno level when the expectation was requests are routed to free dynos. Heroku admits this is a problem. So poor load balancing combined with RoR single threading = poor performance, one that adding more dynos and spending more money won't necessarily help. While it seems clear Heroku didn't make this aspect of their system crystal clear, the incident has generated a lot of teaching moments, if you slog through it all. This is a developing story.
- You need money to feed the beast. Fred Wilson has some revenue ideas for you: Paid App Downloads - ex. WhatsApp; In-app purchases - ex. Zynga Poker; In-app subscriptions - ex. NY Times app; Advertising - ex. Flurry, AdMob; Digital-to-physical - ex. Red Stamp, Postagram; Transactions - ex Hailo.
Don't miss all that the Internet has to say on Scalability, click below and become eventually consistent with all scalability knowledge...
Return to Article