# ElasticSearch as primary database and other solutions

**URL:** <https://discuss.elastic.co/t/elasticsearch-as-primary-database-and-other-solutions/283021>\
**Category:** Elasticsearch\
**Created:** [September 1, 2021, 10:23am UTC](https://discuss.elastic.co/t/elasticsearch-as-primary-database-and-other-solutions/283021 "2021-09-01T10:23:30Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![xemyleex](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xemyleex/32/56623_2.png) [@xemyleex](https://discuss.elastic.co/u/xemyleex)\
**Post date:** [September 1, 2021, 2:58pm UTC](https://discuss.elastic.co/t/elasticsearch-as-primary-database-and-other-solutions/283021/5 "2021-09-01T14:58:31Z")

</div>

Some people says that there could be loss of data:

> [@Elasticsearch as a primary database](https://discuss.elastic.co/t/elasticsearch-as-a-primary-database/85733/9):
>
> 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 tryin…

Other people says that it's not a good idea to use Elasticsearch as primary database in general.

Are they wrong?

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-as-primary-database-and-other-solutions/283021)._