91d437f0fb56cfb5b64de81b60bd6738

I discussed the subject with one of colleagues who is a Cloud Computing architect. I’m logging what my comment here

=-=-

To continue our previous talk is a huge discussion. I’d recommend you could start to get involved in http://twitter.com and follow

http://twitter.com/mashable
http://twitter.com/j3ffyang -> me
http://twitter.com/OpenIBM -> I own this too as of being admin for IBM Open Source Global community

When you hit any of above, you can see the bytes come from http://aws.amazon.com actually, which is an IaaS with no doubt. Twitter is a kind of social collaboration network -> an application running over Amazon Web Services (AWS). Twitter doesn’t own any hardware resources. Whenever Twitter needs computing capability, it goes to AWS and AWS fulfills its request… on demand. Even though Twitter sometimes out of service due to its overload.

@ IaaS, AWS not only gives power of hardware (CPU, memory, disk and network…), but also provides plugin / API to connect Twitter with Hadoop… and Simple Queue Service (SQS), and Simple Database (SDB).

You shouldn’t be surprised @ Twitter’s power to gather thousand of thousand developers around it, if keeping our eyes open. (Some reasons of the motivation of social collaboration in term of Web2.0). See these:

http://tweetwheel.com
http://ftags.com
http://tweetvalue.com/
http://www.tweetizen.com/
http://twittersnooze.com/
http://mrtweet.net/home/j3ffyang
http://tweettrail.com/search/hadoop
…
…

This list is almost endless. They’re all independent of twitter.com. The above are all SaaS, plugable into Twitter.com where provides API -> http://apiwiki.twitter.com/ and http://twitter.com/downloads – @ PaaS

This is an ecosystem.