Well, if it's too large compared to sqlite maybe it doesn't make sense. But I was thinking calling data is not always fixed. Depending on what you use FS for, you might want to get a CDR with many different data linked to each call, even different kinds of data linked to different calls, that would make each call very different and variable in its structure, which would fit a document db model.
Hi Nicolas,Just off the top of my head, but I think couchDB is rather large compared to sqlite, and I think it's also geared more towards storing dynamic datasets...rather ones that can be structured...like FS calling data can.But I might be wrong :)your buddy.--mattOn Mon, Apr 13, 2009 at 12:00 PM, Nicolas Brenner <nicolas@medularis.com> wrote:
_______________________________________________Hi, I am not very familiar with FS internals, but I recently found this "new" db engine called couchDB. Looks pretty interesting, and its main focus is scalability.Has anybody played with couchDB? does it make sense to replace sqlite with couchDB in FS?Here's a link to the project homepage:And here's a video of a presentation given by one of the lead programmers:
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org