Simplify your laptop buyingAs 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
Over on Interop Systems, Jeff Gould has posted a series about AMQP (Advanced Message Queuing Protocol) an open source protocol that takes the place of expensive apps like IBM MQ Series and Tibco Rendezvous.
It's still early days for AMQP with a small number of live implementations but the opportunity to displace the existing monopoly is huge. I've written in the past about how RabbitMQ could be a scaling answer for Twitter as one example.
You might be wondering - how can these guys get away with stonewalling on such a basic requirement as interoperability? The answer is simple. According to Gartner, IBM and Tibco between them control a whopping 93% of the MOM market, which the research firm estimates will be worth around $725 million this year. With a market share like that, IBM and Tibco can pretty much charge whatever they like (using IBM's arcane "processor value unit" pricing scheme, WebSphere MQ will cost you tens of thousands of dollars per processor).
In short, IBM and Tibco share a cozy and lucrative duopoly that no conventional challenger is likely to upset. Customers have little choice but to play ball with them, even when they thumb their noses at interoperability.
- prev
- 1
- next
