So all of this Twitter talk has me thinking about how I would create a massively scalable Twitter-like service on the fabric- Since I threw out the challenge about creating your own .NET Twitter using a fabric. Something along the lines of what Twitterverse is doing might be interesting.

So the basic idea is a fabric application that could consume thousands of messages (I would like to say per second, but I don't think our network admin would appreciate the sustained bandwidth grab - but we'll see) via the twitter public timeline API and do some near real time analytics via the fabric.

I've got the client portion of this application done already and you can see what the twitter public_timeline.xml REST service returns below -

<status>
<created_at>Mon Apr 10 16:27:36 +0000 2007</created_at>
<id>12345678</id>
<text>Put your message here</text>
<user>
<id>1234567</id>
<name>Mark Sundt</name>
<screen_name>marksu</screen_name>
<location>St. Louis</location>
<description>Technology Evangelist</description>
<profile_image_url></profile_image_url>
<url>http://www.appistry.com/blogs/marksu</url>
<protected>false</protected>
</user>
</status>

Since Twitterverse has the key-world cloud covered, I'm thinking about something that can use the above data that might be a little more computationally intensive. So, I've got some ideas, but if you have any drop me a line!

I'll post my code over the next couple of weeks as we flesh out the solution...

Until next time..

Mark