# Using Elasticsearch as primary database

**URL:** <https://discuss.elastic.co/t/using-elasticsearch-as-primary-database/291694>\
**Category:** Elasticsearch\
**Created:** [December 13, 2021, 5:01pm UTC](https://discuss.elastic.co/t/using-elasticsearch-as-primary-database/291694 "2021-12-13T17:01:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lylian1](https://avatars.discourse-cdn.com/v4/letter/l/e9c0ed/32.png) [@Lylian1](https://discuss.elastic.co/u/Lylian1)\
**Post date:** [December 13, 2021, 5:01pm UTC](https://discuss.elastic.co/t/using-elasticsearch-as-primary-database/291694/1 "2021-12-13T17:01:53Z")

</div>

Some blogs say that Elasticsearch is reliable enough to be used as a primary database and some say that Elasticsearch has issues and can loose data.

In order to implement a new project , we have as requirements:

- store of a large amount of sensitive data with retention period
- create dashboard Kibana to perform querying and visualizing data  
A pre-calculation of data volume gives:
- About 35 million records each year with 5KB.
- Assuming we store data over a 10 year period, we can reach 5T (due to data growth).

We chose Elasticsearch as a data storage, indexing and analysis tool.  
Could Elasticsearch be used as a primary database without data loss risk or we should use another database to store data?

Thanks.

---

<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:** [January 10, 2022, 5:02pm UTC](https://discuss.elastic.co/t/using-elasticsearch-as-primary-database/291694/2 "2022-01-10T17:02:23Z")

</div>

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