Hello<div><br></div><div>very interesting issue actually...the mtree module fits perfectly well in a key-value model becaue basically is what the mtree table structure defines; that's why redis was the first thing that came to my mind when I saw the redis module. Two problems with redis:</div>
<div>-no "native" mt_match function, up to the user to find the best option</div><div>-replication. Until the cluster feature is ready, we need to change by hand the server ip address, which implies a kamailio restart. There is no mi command for changing the server in the fly, right..(not in the module documentation at least)?</div>
<div><br></div><div>Daniel, I agree that your suggestion about the mi/rpc method would be nice. I will also take a look at Mongo as Douglas suggests, and especially CouchDB, because you can talk to Couch DB via http...</div>
<div><br></div><div>Regards</div><div><br></div><div>Javi<br><br><div class="gmail_quote">On Mon, Nov 14, 2011 at 1:32 PM, Douglas Hubler <span dir="ltr"><<a href="mailto:douglas@hubler.us">douglas@hubler.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Mon, Nov 14, 2011 at 5:10 AM, Daniel-Constantin Mierla<br>
<<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>> wrote:<br>
> are there any other no-sql database systems that have such mechanism? Might<br>
> not be hard to make a connector when the time will allow -- just to know the<br>
> best options here.<br>
<br>
</div>mongodb will auto promote. Caveat, (like redis if i understand<br>
correctly), is that all writes are directed to a single master (be it<br>
chosen dynamically), but reads can happen anywhere to spread the load.<br>
Also, you need to accept the distaster scenario of a "network<br>
partition" where a minority set of servers find themselves w/o a<br>
master. Example: 5 servers in datacenter #1 and 4 servers in<br>
datacenter #2. If the link between datacenters is broken, then all<br>
servers in datacenter #2 will not have a master and will be read-only<br>
until link is restored. Good part about single master is there's no<br>
chance of inconsistent data.<br>
<br>
Turns out local fail-over v.s. consistent data is a well explored area.<br>
<br>
<a href="http://blog.nahurst.com/visual-guide-to-nosql-systems" target="_blank">http://blog.nahurst.com/visual-guide-to-nosql-systems</a><br>
<br>
I've worked w/the C++ driver to mongodb is anyone has questions.<br>
</blockquote></div><br></div>