# Couchdb vs elasticsearch **URL:** \ **Category:** Elasticsearch\ **Created:** [September 12, 2010, 7:18pm UTC](https://discuss.elastic.co/t/couchdb-vs-elasticsearch/3324 "2010-09-12T19:18:46Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![fede\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fede_2/32/3320_2.png) [@fede\_2](https://discuss.elastic.co/u/fede_2)\ **Post date:** [September 12, 2010, 7:18pm UTC](https://discuss.elastic.co/t/couchdb-vs-elasticsearch/3324/1 "2010-09-12T19:18:46Z")
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 ---
**Author:** ![James\_Cook](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@James\_Cook](https://discuss.elastic.co/u/James_Cook)\ **Post date:** [September 12, 2010, 8:45pm UTC](https://discuss.elastic.co/t/couchdb-vs-elasticsearch/3324/2 "2010-09-12T20:45:43Z")
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](mailto:federico.dayan@gmail.com) wrote: > This might be a stupid question, but I do not see differences with > couchdb and Elasticsearch. > > They could solve the same problem , but I see a great advantage of > Elasticsearch 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 Elasticsearch it's not a database, but it could work as one.. > > Thanks, > > Federico ---
**Author:** ![Lukas\_Kahwe\_Smith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas_kahwe_smith/32/3264_2.png) [@Lukas\_Kahwe\_Smith](https://discuss.elastic.co/u/Lukas_Kahwe_Smith)\ **Post date:** [September 12, 2010, 9:10pm UTC](https://discuss.elastic.co/t/couchdb-vs-elasticsearch/3324/3 "2010-09-12T21:10:26Z")
On 12.09.2010, at 21:18, Fede wrote: > This might be a stupid question, but I do not see differences with > couchdb and Elasticsearch. > > They could solve the same problem , but I see a great advantage of > Elasticsearch 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 Elasticsearch 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](mailto:mls@pooteeweet.org) ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [September 13, 2010, 9:57am UTC](https://discuss.elastic.co/t/couchdb-vs-elasticsearch/3324/4 "2010-09-13T09:57:19Z")
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.org](mailto:mls@pooteeweet.org)wrote: > On 12.09.2010, at 21:18, Fede wrote: > > > This might be a stupid question, but I do not see differences with > > couchdb and Elasticsearch. > > > > They could solve the same problem , but I see a great advantage of > > Elasticsearch 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 Elasticsearch 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](mailto:mls@pooteeweet.org) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:19am UTC](https://discuss.elastic.co/t/couchdb-vs-elasticsearch/3324/5 "2017-07-06T04:19:23Z")