Couchdb vs elasticsearch


(fede-2) #1

This might be a stupid question, but I do not see differences with
couchdb and elastic search.

They could solve the same problem , but I see a great advantage of
elastic search over couchdb

if you want to search on couch db, you have to write a map reduce

is there something that I'm missing

Is there fundamental difference that one cannot solve a problem of the
other

I know elastic search it's not a database, but it could work as one..

Thanks,

Federico


(James Cook) #2

We are using it as a database.

IMHO it has richer query capabilities and better sharding/partitioning than
what was available for MongoDB at the time. Of course, ES is a work in
progress while CouchDB is stable and maturing.

Writing queries is very painful however. They are proving to be difficult to
learn for someone like me without a Lucene or text-search background.
Looking forward to an ES in Action book.

On Sun, Sep 12, 2010 at 3:18 PM, Fede federico.dayan@gmail.com wrote:

This might be a stupid question, but I do not see differences with
couchdb and elastic search.

They could solve the same problem , but I see a great advantage of
elastic search over couchdb

if you want to search on couch db, you have to write a map reduce

is there something that I'm missing

Is there fundamental difference that one cannot solve a problem of the
other

I know elastic search it's not a database, but it could work as one..

Thanks,

Federico


(Lukas Kahwe Smith) #3

On 12.09.2010, at 21:18, Fede wrote:

This might be a stupid question, but I do not see differences with
couchdb and elastic search.

They could solve the same problem , but I see a great advantage of
elastic search over couchdb

if you want to search on couch db, you have to write a map reduce

is there something that I'm missing

Is there fundamental difference that one cannot solve a problem of the
other

I know elastic search it's not a database, but it could work as one..

couchdb has a very unique approach to distribution and more importantly synchronization. furthermore it seems from its foot print it also works quite well in the mobile space. do note that from an search perspective it doesnt compete with lucene, actually there is lucene integration for couchdb for this very reason.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org


(Shay Banon) #4

couchdb has some unique features that really make it stand out compared to
other solutions, of course, assuming you need them. For example, you build
views and stream changes done to them to the client, it has quite a unique
disconnected replication model, and allow you to see history / get stream of
changes (assuming no compaction has been done).

I think that both can play really well together. I am planning to build
something that would automatically index couchdb into elasticsearch.

-shay.banon

On Sun, Sep 12, 2010 at 11:10 PM, Lukas Kahwe Smith mls@pooteeweet.orgwrote:

On 12.09.2010, at 21:18, Fede wrote:

This might be a stupid question, but I do not see differences with
couchdb and elastic search.

They could solve the same problem , but I see a great advantage of
elastic search over couchdb

if you want to search on couch db, you have to write a map reduce

is there something that I'm missing

Is there fundamental difference that one cannot solve a problem of the
other

I know elastic search it's not a database, but it could work as one..

couchdb has a very unique approach to distribution and more importantly
synchronization. furthermore it seems from its foot print it also works
quite well in the mobile space. do note that from an search perspective it
doesnt compete with lucene, actually there is lucene integration for couchdb
for this very reason.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org


(system) #5