# Buffering Elasticsearch results in (non)sql database

**URL:** <https://discuss.elastic.co/t/buffering-elasticsearch-results-in-non-sql-database/61673>\
**Category:** Elasticsearch\
**Created:** [September 28, 2016, 8:42am UTC](https://discuss.elastic.co/t/buffering-elasticsearch-results-in-non-sql-database/61673 "2016-09-28T08:42:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![christoph](https://avatars.discourse-cdn.com/v4/letter/c/eb8c5e/32.png) [@christoph](https://discuss.elastic.co/u/christoph)\
**Post date:** [September 28, 2016, 8:42am UTC](https://discuss.elastic.co/t/buffering-elasticsearch-results-in-non-sql-database/61673/1 "2016-09-28T08:42:02Z")

</div>

We have some requests to elasticsearch that appear much more often than others.  
For example when a user enters our recipe section, we always show some predefined categories, which when clicked generate a Elasticsearch query. On the other hand users can search for random terms.

Is there a benefit to pre calculate the standard queries and serve them from another database?  
My thinking is, that hosting Elasticsearch is quite expensive compared to another database on AWS.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 29, 2016, 5:48am UTC](https://discuss.elastic.co/t/buffering-elasticsearch-results-in-non-sql-database/61673/2 "2016-09-29T05:48:00Z")

</div>

> [@christoph](#):
>
> compared to another database on AWS

Which one?

---

<div class="post-metadata">

**Author:** ![christoph](https://avatars.discourse-cdn.com/v4/letter/c/eb8c5e/32.png) [@christoph](https://discuss.elastic.co/u/christoph)\
**Post date:** [September 29, 2016, 7:40am UTC](https://discuss.elastic.co/t/buffering-elasticsearch-results-in-non-sql-database/61673/3 "2016-09-29T07:40:54Z")

</div>

I thought in general, since I need more RAM/CPU for the same number for request, but I might be very wrong.

---

<div class="post-metadata">

**Author:** ![JoarSvensson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joarsvensson/32/8740_2.png) [@JoarSvensson](https://discuss.elastic.co/u/JoarSvensson)\
**Post date:** [September 29, 2016, 9:20am UTC](https://discuss.elastic.co/t/buffering-elasticsearch-results-in-non-sql-database/61673/4 "2016-09-29T09:20:41Z")

</div>

I would suggest you have a proper cache in place, for example Varnish to solve your issue. To me your approach is not a question of using any other datastore really. Elasticsearch is basically fast enough in most cases.

---

<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:** [July 5, 2017, 10:16pm UTC](https://discuss.elastic.co/t/buffering-elasticsearch-results-in-non-sql-database/61673/5 "2017-07-05T22:16:12Z")

</div>