Do We Scale Usage, or Features?

Apart from being a rude shoot down of an already established failing, I want to understand what does SMSGupshup have that needs to be scaled? There’s no word tracking, no API, not even a jacktastic @scobleizer to throttle the system. It seems like a simple receive-SMS-push-SMS system. I don’t see a hundred third party applications trying to retrieve messages (gupshup?) from their servers.

Sure they have 3 times more users, who send in one line messages what, every hour (since SMS rates keep such premium services at bay)? . They have 10 million plus messages, that just need to go out and be stored. I’m sorry, but I just don’t see what they need to scale apart from a growing database.

✓ Sunday, 15 June '08

[…] few weeks back I link listed a make-an-example-of type post which compared Twitter and SMSgupshup based on scalability. I will […]


Leave a comment

You can use all presentational tags, but I prefer if you use Markdown. It's just easier to use.

RSS feed for comments on this post. TrackBack URL

Copyright © 2006-08 Aditya Mukherjee | Valid XHTML 1.0 Transitional Valid CSS!