VoIP Mailing List Archives

[nicolas at medularis.com]

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:
- http://couchdb.apache.org/



And here's a video of a presentation given by one of the lead programmers:
- http://www.vimeo.com/1992869

[mattdfong at gmail.com]

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.


--matt

On Mon, Apr 13, 2009 at 12:00 PM, Nicolas Brenner <nicolas@medularis.com (nicolas@medularis.com)> wrote:

[nicolas at medularis.com]

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.

Thinking a bit more now, since couchdb is a document-based DB, it might be good for configuration-generating applications, like the ones consumed by xml_curl. These are external applications, yet they are still very closely related to FS, and might be able to benefit from using something like couchdb.

On Mon, Apr 13, 2009 at 1:06 AM, Matthew Fong <mattdfong@gmail.com (mattdfong@gmail.com)> wrote:

[jason at jasonjgw.net]

Nicolas Brenner <nicolas@medularis.com> wrote:

[grevenx at me.com]

The only part I see fit for integration with CouchDB is for storing
CDR documents.
This kind of database is imho best-used for storing large sets of data,
in a document structure.

I don't think the FS config fits this description, since the amount of
config documents are typically not "large".
You can also look at related distributed systems like Hadoop/Hbase,
which could be good to store CDRs in.
It's been a couple of months since I researched these systems, but I
think it's possible to
enable an HTTP REST interface for both, so you could use the built-in
feature for posting CDRs
to a HTTP server.

Best regards,
Even André

On 13. april. 2009, at 07.52, Jason White wrote: