By that, I mean we should talk. By we, I mean anyone who groks the concept of what MySQL CEO Marten Mickos described at the Web 2.0 conference as “the great database in the sky”.

In Mickos’ vision, all the world’s structured data is exposed for consumption over the Internet. There is a DNS server that knows all the SQL databases, there’s some form of clearinghouse or brokerage that manages who can see what and when, there are payment mechanisms, and a host of problems to overcome. But according to Mickos, the fulfillment of the vision allows the data to become the platform.

Micko’s discusses the requirement of a means for real-time data updates, sharing and aggregation of the world’s structured data. This point is critical. The value and relevance of this conceptual database depends on how well it can deliver on the promise of: The right data, to the right person/place/thing at the right time. Meeting this requirement sounds like a job for extremely scalable XML routers that can enable the synchronous flow of structured data. Oddly enough, that’s exactly how we describe Jabber XCP.

As part of this vision, Jabber XCP is the transport mechanism of choice for data providers and clearinghouses that want to make policy-based choices on who can access what data, when they can access it, how they access it and why in real-time.

Based upon our work in government and financial services, we’ve already done a lot of the heavy lifting around access policies for synchronous flows of structured data. Scalability is the subject of an upcoming blog post, but suffice it to say, we’re the only game in town if you’re thinking really, really big.

If you’ve read this far, we should definitely talk.

This entry was posted on Monday, November 13, 2006 at November 13, 2006 and is filed under Commentary, XMPP. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.