Turning Twitter into an application server

As much as Twitter is a powerful communication and social application, it's a relatively simple Web app. As part of a new contest sponsored by Engine Yard, Ruby on Rails developers are going to turn Twitter into their own application server.

The contest asks developers to program the "Worst App Server Technology Ever" (Waste) using Twitter as the message bus. While much of the contest is being done tongue-in-cheek, it's actually an interesting use case to see if a service like Twitter can take the place of a more traditional message bus like IBM MQ series or AMQP (Advanced Message Queuing Protocol).

Contest participants register up to five Twitter handles and code the function that each would perform in a program. When the contest challenge is issued on November 12, participants will have to use at least 10 of the pre-designated Twitter handles (other than their own) as endpoints to perform functions on data sets located at unique URLs. All messages will work through a series of automated public Twitter replies.

This is somewhere between an application server, a social game, the "telephone game" and service-oriented architecture (SOA) where Twitter plays the role of the enterprise service bus and the Twitter API is the broker between data sources. SOA relies on services exposing their functionality other applications and services can read to understand how to utilize those services. In this case, Twitter can be used as an application server in the cloud. (Take that buzzword bingo players.)

The funny thing is that as absurd and comical as this sounded when the Engine Yard guys told me about it, I've started to think about this as a way to possibly achieve a real technological breakthrough. And while I don't think that Twitter will be the "cloud bus," I do think that there is a lot to be learned from applying this type of constraint to a data flow process.

Engine Yard VP of marketing Michael Mullany told me that the contest shows how developers can leverage a relatively straightforward platform in innovative ways. But it's also another example of an interesting marketing effort to use Twitter as the vehicle for one's own benefit. Also, in true open source fashion, developers wind up building new applications based on code written by their peers.

Let's hope Twitter can handle the attention and developers are not greeted by the ever-lurking fail whale. You can check out the contest and learn more details at Engineyard.com

[lmasanti]

What abouot comparing this with Google Wave's posibilities as an app server?
I do know that GW still does not prime time, but it already has an app developing concept.

[thinksketchdesign]

yes exactly. The way I see it, that is why Google Wave is so important and exciting. Twitter made us realize that an exercise like this was possible. And the Google Wave protocol is the architecture that will make this kind of exercise practical. A cloud server that is public and operates in real-time - that's amazing. Don't see why it's important yet? Here's one little example I like: Imagine Obama giving a speech. Imagine crowd-sourcing an instant translation of the speech into every language that pops up on your screen while he's talking. That's the kind of thing that twitter made us dream about, and that Google Wave will actually make happen. At least, that's how I see it.

http://www.thinksketchdesign.com/2009/10/27/web/in-twitters-wake-head-scratching-persists-a-real-time-network-revolution-bides-its-time

[Hunnter2k3]

Botnets already use Twitter a lot.
If Botnets are using it, it should be capable of handling your average application server "bus".

I'd be pretty impressed if it was coded in such a way that it could chain several tweets at a time, or even use a "pointer" of sorts to refer, relatively, to an older tweet.

[robinhukes]

hy nice and informativenews,,,,,,,,,,,,,

http://www.goarticles.com/cgi-bin/showa.cgi?C=2145820

[VoiceOfLogic]

I had gotten Twitter to rake my leaves the other day. Tomorrow I should have it ready to brush my teeth for me.