# Several applications sharing the same cluster

**URL:** <https://discuss.elastic.co/t/several-applications-sharing-the-same-cluster/44535>\
**Category:** Elasticsearch\
**Created:** [March 16, 2016, 9:36am UTC](https://discuss.elastic.co/t/several-applications-sharing-the-same-cluster/44535 "2016-03-16T09:36:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jvskriubakken](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jvskriubakken/32/8507_2.png) [@jvskriubakken](https://discuss.elastic.co/u/jvskriubakken)\
**Post date:** [March 16, 2016, 9:36am UTC](https://discuss.elastic.co/t/several-applications-sharing-the-same-cluster/44535/1 "2016-03-16T09:36:16Z")

</div>

Hi!

We have just started to use Elasticsearch at my work - and in at least two applications and possibly three in the future. We are going to host the cluster (or clusters) our selves, and a question which has then arisen is whether we should let several applications share the same cluster and create each their index within it or each application has their own cluster. The operation team would prefer one cluster to monitor, but as a developer I feel sceptical about it - as different applications would have different needs that would be difficult to combine.

Would any one like to share their thoughts or experiences on this matter?

Most grateful for any guidance!

Jørund

---

<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:** [March 18, 2016, 2:33am UTC](https://discuss.elastic.co/t/several-applications-sharing-the-same-cluster/44535/2 "2016-03-18T02:33:55Z")

</div>

You can totally put similar use cases together, but;

> [@jvskriubakken](#):
>
> different applications would have different needs that would be difficult to combine.

This 🙂

---

<div class="post-metadata">

**Author:** ![jvskriubakken](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jvskriubakken/32/8507_2.png) [@jvskriubakken](https://discuss.elastic.co/u/jvskriubakken)\
**Post date:** [March 29, 2016, 7:31am UTC](https://discuss.elastic.co/t/several-applications-sharing-the-same-cluster/44535/3 "2016-03-29T07:31:03Z")

</div>

Thanks for confirming that.

Would you have time elaborate or give some examples?

Most appreciated!

---

<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:** [March 29, 2016, 10:46am UTC](https://discuss.elastic.co/t/several-applications-sharing-the-same-cluster/44535/4 "2016-03-29T10:46:35Z")

</div>

To me it would depend on how different the requirements are. Using different indexes is of course a common approach.

For example you can look at how Elastic has choosen to handle this for Kibana. Settings in Kibana is stored in a different index with custom template. Other applications such as Timelion and the to be Graph app is probably storing settings in a similar way.

By using the same cluster (for production), you'll be able to query, aggregate and "share" information between your 3 applications if necessary. That's much more difficult to handle between clusters.

---

<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, 11:04pm UTC](https://discuss.elastic.co/t/several-applications-sharing-the-same-cluster/44535/5 "2017-07-05T23:04:27Z")

</div>