# Is it okay to keep product data only in Elasticsearch?

**URL:** <https://discuss.elastic.co/t/is-it-okay-to-keep-product-data-only-in-elasticsearch/113553>\
**Category:** Elasticsearch\
**Created:** [December 29, 2017, 8:57am UTC](https://discuss.elastic.co/t/is-it-okay-to-keep-product-data-only-in-elasticsearch/113553 "2017-12-29T08:57:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Piyush\_Aggarwal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/piyush_aggarwal/32/27306_2.png) [@Piyush\_Aggarwal](https://discuss.elastic.co/u/Piyush_Aggarwal)\
**Post date:** [December 29, 2017, 8:57am UTC](https://discuss.elastic.co/t/is-it-okay-to-keep-product-data-only-in-elasticsearch/113553/1 "2017-12-29T08:57:24Z")

</div>

Hello, I am trying to build an e-commerce platform in which I am going to put the products into the elasticsearch Index. I am referencing [this](https://project-a.github.io/on-site-search-design-patterns-for-e-commerce/) for the modeling of the Product. Is it okay to keep the products only in the elasticsearch Index? or to be safe I must use some other database storage? I am currently using Aerospike(A key-value NoSQL database) for storing other data models.

---

<div class="post-metadata">

**Author:** ![morphers82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/morphers82/32/22904_2.png) [@morphers82](https://discuss.elastic.co/u/morphers82)\
**Post date:** [December 29, 2017, 6:41pm UTC](https://discuss.elastic.co/t/is-it-okay-to-keep-product-data-only-in-elasticsearch/113553/2 "2017-12-29T18:41:39Z")

</div>

as long as you have a really good backup replication scheme I don't see why not

---

<div class="post-metadata">

**Author:** ![west415](https://avatars.discourse-cdn.com/v4/letter/w/919ad9/32.png) [@west415](https://discuss.elastic.co/u/west415)\
**Post date:** [December 29, 2017, 9:47pm UTC](https://discuss.elastic.co/t/is-it-okay-to-keep-product-data-only-in-elasticsearch/113553/3 "2017-12-29T21:47:20Z")

</div>

Personally, I would use a typical transactional database storage for your e-commerce store and that would be the single source of the truth. I would then push data into your elastic index for search. Other's may disagree, but that's what I would suggest.

Your transactional database would be more normalized and your elastic index would be more flattened out and easy to query using their REST API.

When a new record is created on my transactional database, I then make an HTTP POST to create the same record in elastic.

---

<div class="post-metadata">

**Author:** ![Piyush\_Aggarwal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/piyush_aggarwal/32/27306_2.png) [@Piyush\_Aggarwal](https://discuss.elastic.co/u/Piyush_Aggarwal)\
**Post date:** [January 5, 2018, 6:44am UTC](https://discuss.elastic.co/t/is-it-okay-to-keep-product-data-only-in-elasticsearch/113553/4 "2018-01-05T06:44:54Z")

</div>

Can you suggest me some product data model that is normalized just like mentioned in [here](https://project-a.github.io/on-site-search-design-patterns-for-e-commerce/)?

---

<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:** [February 2, 2018, 6:45am UTC](https://discuss.elastic.co/t/is-it-okay-to-keep-product-data-only-in-elasticsearch/113553/5 "2018-02-02T06:45:18Z")

</div>

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