# Elasticsearch as a primary database

**URL:** <https://discuss.elastic.co/t/elasticsearch-as-a-primary-database/85733>\
**Category:** Elasticsearch\
**Created:** [May 15, 2017, 9:59am UTC](https://discuss.elastic.co/t/elasticsearch-as-a-primary-database/85733 "2017-05-15T09:59:33Z")\
**Posts on this page:** 1\
**Showing post:** 9

<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:** [May 16, 2017, 5:45am UTC](https://discuss.elastic.co/t/elasticsearch-as-a-primary-database/85733/9 "2017-05-16T05:45:52Z")

</div>

> Some customers use Elasticsearch as a primary datastore, some set-up comprehensive back-up solutions using features such as our Snapshot and Restore, while others use Elasticsearch in conjunction with a data storage system like Hadoop or even flat files. Elasticsearch can be used for so many different use cases which is why we have created this page to make sure you are fully informed when you are architecting your system.

Basically you are aware that something can hoes wrong but we are trying hard to make that never happen

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-as-a-primary-database/85733)._