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".
Nicolas Brenner 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?
I think a
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
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
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:
- ht
