# Elasticsearch solo vs Couchbase+Elasticsearch

**URL:** <https://discuss.elastic.co/t/elasticsearch-solo-vs-couchbase-elasticsearch/35785>\
**Category:** Elasticsearch\
**Created:** [November 27, 2015, 6:33pm UTC](https://discuss.elastic.co/t/elasticsearch-solo-vs-couchbase-elasticsearch/35785 "2015-11-27T18:33:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![esnosek](https://avatars.discourse-cdn.com/v4/letter/e/a6a055/32.png) [@esnosek](https://discuss.elastic.co/u/esnosek)\
**Post date:** [November 27, 2015, 6:33pm UTC](https://discuss.elastic.co/t/elasticsearch-solo-vs-couchbase-elasticsearch/35785/1 "2015-11-27T18:33:10Z")

</div>

Let me describe the issue. Now I'm at the stage of architectural  
changes. I used to use Elasticsearch as aggregation and search tool, but  
now I'm thinking about use it as main DB. I read that there is not  
recommended to use Elasticsearch as a main DB, only as a index. So I  
read presentation about connection it with Couchbase:

> **[nosql13-bcn-couchbase-elasticsearch-jeroen-reijn.pdf](https://2013.nosql-matters.org/bcn/wp-content/uploads/2013/12/nosql13-bcn-couchbase-elasticsearch-jeroen-reijn.pdf)**
>
> 2.52 MB

I downloaded and installed Couchbase and plugin for integration with Elasticsearch

> **[couchbaselabs/elasticsearch-transport-couchbase](https://github.com/couchbaselabs/elasticsearch-transport-couchbase)**
>
> elasticsearch-transport-couchbase - A plugin for ElasticSearch that enables loading data using Couchbase XDCR

I'm not convinced about this solution. Firstly, aggregation is faster  
in Elasticsearch. Secondly, Elasticsearch supports histogram,  
geopoints, full text search and many other, so it seems that only reason  
to keep Couchbase is not to have Elasticsearch as the main DB.

So my question is about the benefits of integration Elasticsearch with Couchbase in my case?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 27, 2015, 8:11pm UTC](https://discuss.elastic.co/t/elasticsearch-solo-vs-couchbase-elasticsearch/35785/2 "2015-11-27T20:11:11Z")

</div>

You can have couchbase as the datastore, source of truth, and use elasticsearch for all the other things: aggs, search, get, whatever.

If your data are not sensible, like logs, then you can use elasticsearch only.  
If not, you need to be able to reindex in any case. So keep your source of truth somewhere, filesystem, hdfs, database, couchbase... Wherever. In case of problem, you will be able to reindex.

Have a look also at this page: [https://www.elastic.co/guide/en/elasticsearch/resiliency/current/index.html](https://www.elastic.co/guide/en/elasticsearch/resiliency/current/index.html)

---

<div class="post-metadata">

**Author:** ![esnosek](https://avatars.discourse-cdn.com/v4/letter/e/a6a055/32.png) [@esnosek](https://discuss.elastic.co/u/esnosek)\
**Post date:** [January 12, 2016, 5:53pm UTC](https://discuss.elastic.co/t/elasticsearch-solo-vs-couchbase-elasticsearch/35785/3 "2016-01-12T17:53:05Z")

</div>

Thank you for help. Now I know your answer was very helpful.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:25pm UTC](https://discuss.elastic.co/t/elasticsearch-solo-vs-couchbase-elasticsearch/35785/4 "2017-07-05T23:25:07Z")

</div>