What about NoSQL over xmpp?

flossy · June 12th, 2010, 07:07 AM

Due to my thoughts about persistence in xmpp applications I got an idea:
Why not get access to the database directly over xmpp?

For example we could do something like this:

Get documents

Code:

<iq type="get" from="[email protected]" to="[email protected]" id="query1">
  <nosql type="get">
    <doc id="3f2458e368e3687a68797321ea687135b"/>
  <nosql/>
</iq>

with a result like this

Code:

<iq type="result" from="[email protected]" to="[email protected]" id="query1">
  <nosql type="result">
    <doc id="3f2458e368e3687a68797321ea687135b">
      [DOCUMENT CONTENT]
    </doc>
  </nosql>
</iq>

Get view

Code:

<iq type="get" from="[email protected]" to="[email protected]" id="query4">
  <nosql type="get"> 
    <view id="tasks" limit="5"/>
  </nosql>
</iq>

Code:

<iq type="result" from="[email protected]" to="[email protected]" id="query4">
  <nosql type="result"> 
    <view>
      <row id="365435435354">
	 <doc id="9873543568">[DOCUMENT CONTENT]</doc>
	</row>
      <row id="68798351687" >
	<doc id="877565654364">[DOCUMENT CONTENT]</doc>
      </row>
    </view>
  </nosql>
</iq>

What do you think about ti? Is it bull****? Or are there better ways to access a database over xmpp?

ka_el · June 13th, 2010, 07:49 PM

You might be interested by the XEP-0043: Jabber Database Access.

metajack · June 28th, 2010, 02:22 PM

This is a very neat idea. One thing it buys you is streaming results and asynchronous notifications, which aren't something you can easily get over HTTP.

XML serialization is going to hurt a bit though.