# Is the User-Based Data model a good solution?

**URL:** <https://discuss.elastic.co/t/is-the-user-based-data-model-a-good-solution/158523>\
**Category:** Elasticsearch\
**Created:** [November 28, 2018, 9:25am UTC](https://discuss.elastic.co/t/is-the-user-based-data-model-a-good-solution/158523 "2018-11-28T09:25:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mgrabazey](https://avatars.discourse-cdn.com/v4/letter/m/ea666f/32.png) [@mgrabazey](https://discuss.elastic.co/u/mgrabazey)\
**Post date:** [November 28, 2018, 9:25am UTC](https://discuss.elastic.co/t/is-the-user-based-data-model-a-good-solution/158523/1 "2018-11-28T09:25:30Z")

</div>

Hi everyone!

Sorry for my bad English.

I am researching a data model for storing product reviews. Suppose, need to store reviews of 10000+ products. I think the [User-Based Data](https://www.elastic.co/guide/en/elasticsearch/guide/current/user-based.html) model is right here.  
But it says here that for products that has only few reviews it makes no sense to create a separate index. Initially this will be the case: all products will have a small amount of feedback. But over time, the number of reviews for some products may increase significantly!

Here comes the [One Big User](https://www.elastic.co/guide/en/elasticsearch/guide/current/one-big-user.html) model. But it is not easy to implement: need to monitor the products, make a decision that it is time to make a separate index, create index and move data...

Maybe there is some automation for this?

And if implement User-Based Data model, how bad will it be if 90% of products will have 10-20 reviews (indices of 10-20 documents), and 10% with 1000+ reviews?

Thank you!

---

<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:** [December 26, 2018, 9:25am UTC](https://discuss.elastic.co/t/is-the-user-based-data-model-a-good-solution/158523/2 "2018-12-26T09:25:39Z")

</div>

Closed on December 26, 2018, 9:25am UTC

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