Monday, October 5, 2009


Last year, a number of tech blogs started to realize the reason why Twitter has had consistent disruptions to their service: over capacity due to Ruby on Rails. The framework that Twitter was built upon wasn't designed to be truly scaleable. At least, not to the degree where web users, cellphone users and media outlets have been slamming their servers. In light of this, it poses several questions which both relate to each other:

  1. How to handle this dilemma?
  2. How much will it cost?

Solving a problem like this is only limited to the budget they're willing to invest into it. Like a lot of people, I still have no clue as to how Twitter generates any revenue. They can get $100m from venture capitalists, but businesses with such explosive growth and no real sustainable business model begs to question how they intend to survive. Was Twitter built with the intention on being purchased?

No comments:

Post a Comment