# Will it be good to use elasticsearch where there are numerous updates

**URL:** <https://discuss.elastic.co/t/will-it-be-good-to-use-elasticsearch-where-there-are-numerous-updates/97523>\
**Category:** Elasticsearch\
**Created:** [August 18, 2017, 7:11am UTC](https://discuss.elastic.co/t/will-it-be-good-to-use-elasticsearch-where-there-are-numerous-updates/97523 "2017-08-18T07:11:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amit\_Shah](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amit_shah/32/20805_2.png) [@Amit\_Shah](https://discuss.elastic.co/u/Amit_Shah)\
**Post date:** [August 18, 2017, 7:11am UTC](https://discuss.elastic.co/t/will-it-be-good-to-use-elasticsearch-where-there-are-numerous-updates/97523/1 "2017-08-18T07:11:32Z")

</div>

I was looking in using elasticsearch as my desired database as it is very impressive architecture and performing system. One thing i noticed was .. for every index updated, there is a version being created. If not mistaken, it dose stores the older versioned objects too.. as elastic indexes seems to be immutable. Now in such a scenario, the data space is going to exponentially explode in case of me having a scenario .. where i constantly update a certain set of values.  
Correct me if i am wrong in my interpretation about my system.

I wanted to understand . in such a scenario - will it be a good option to have elasticsearch as an option to go for or will you recommend me some other solution.

Please enlighten me.

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [August 18, 2017, 7:32am UTC](https://discuss.elastic.co/t/will-it-be-good-to-use-elasticsearch-where-there-are-numerous-updates/97523/2 "2017-08-18T07:32:14Z")

</div>

Hey,

indeed Elasticsearch is an append only datastore. Once a document is written to disk, it is immutable. However there is a regular clean up process going on called merging, which rewrites your data and is removing all the documents that are marked as deleted.

Also, Elasticsearch does not keep revisions of documents around. You can access the latest version and that's it. Others will be removed over time due to merging.

See [https://www.elastic.co/guide/en/elasticsearch/reference/5.5/index-modules-merge.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.5/index-modules-merge.html)

---

<div class="post-metadata">

**Author:** ![Amit\_Shah](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amit_shah/32/20805_2.png) [@Amit\_Shah](https://discuss.elastic.co/u/Amit_Shah)\
**Post date:** [August 18, 2017, 8:06am UTC](https://discuss.elastic.co/t/will-it-be-good-to-use-elasticsearch-where-there-are-numerous-updates/97523/3 "2017-08-18T08:06:18Z")

</div>

Awsome... That was a relief for me to know the fact. Now I am more inclined  
towards having Elasticsearch as prominent solution.

---

<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:** [September 15, 2017, 8:06am UTC](https://discuss.elastic.co/t/will-it-be-good-to-use-elasticsearch-where-there-are-numerous-updates/97523/4 "2017-09-15T08:06:24Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.