Digital Carnival

As I mentioned in a previous post  I’ve been thinking a lot lately about alternative service architectures to support Internet based communication. At one point I went so far as to consider rekindling my love for ACE to maybe build one myself. I certainly took a good look (one that’s not necessarily finished yet) at BlazeDS due to the fact that I’ve been playing with AIR using Flex lately.

Another thing that caught my eye is recent developments and buzz around XMPP. You may be most familiar with it as the protocol that powers Jabber (and GTalk, as it is based on Jabber). I thought I would use this post as a link source of some of the stuff I have found on XMPP, Jabber and ejabberd to highlight it’s potential uses.

Good starting points:

• Could Instant Messaging (XMPP) Power the Future of Online Communication? (ReadWriteWeb)
• Is XMPP the ‘Next Big Thing’ (Slashdot)
• ntroducing the XMPP application server: The Twitter example (Process One)
• XMPP (a.k.a. Jabber) is the future for cloud services (jivetalks)

XMPP appears to have it all:

• Distributed (cloud) services, secure within the individual entry points.
• The promise to end all the hacks to make the web work, not how it was meant to, but how we choose to use it.
• Controlled scalability
• The end of service polling.
• Growing support from Apple, Google, IBM and others.

As a developer, architect or even technologist this is something that should not be ignored. Topics like The Semantic Web and Web 3.0 (?!?!) abound, here’s a topic that has all the makings of the next big Internet thing