# Elasticsearch persistance mechanism

**URL:** <https://discuss.elastic.co/t/elasticsearch-persistance-mechanism/54956>\
**Category:** Elasticsearch\
**Created:** [July 7, 2016, 2:40pm UTC](https://discuss.elastic.co/t/elasticsearch-persistance-mechanism/54956 "2016-07-07T14:40:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Meriem\_Rezgui](https://avatars.discourse-cdn.com/v4/letter/m/ecc23a/32.png) [@Meriem\_Rezgui](https://discuss.elastic.co/u/Meriem_Rezgui)\
**Post date:** [July 7, 2016, 2:40pm UTC](https://discuss.elastic.co/t/elasticsearch-persistance-mechanism/54956/1 "2016-07-07T14:40:17Z")

</div>

i'm developping a java application which will allow me to insert and extract data from Elasticsearch and create indexs . i wanted to know if i have to use hibernate (or another mechanism) or if elasticsearch have its own persistance mechanism.  
Thanks in advance for your help

---

<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:** [July 7, 2016, 3:24pm UTC](https://discuss.elastic.co/t/elasticsearch-persistance-mechanism/54956/2 "2016-07-07T15:24:42Z")

</div>

Elasticsearch stores data on disk.

Depending on how critical your data is, you may want to keep another copy of your data somewhere else:

- in a database / a filesystem / whatever
- as backups by running snapshot API often enough

May be you'd also read [the resiliency status page](https://www.elastic.co/guide/en/elasticsearch/resiliency/current/index.html).

---

<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, 10:37pm UTC](https://discuss.elastic.co/t/elasticsearch-persistance-mechanism/54956/3 "2017-07-05T22:37:19Z")

</div>

Closed on July 5, 2017, 10:37pm UTC