# Multiple Elasticsearch instances architecture

**URL:** <https://discuss.elastic.co/t/multiple-elasticsearch-instances-architecture/333187>\
**Category:** Elasticsearch\
**Created:** [May 11, 2023, 10:18am UTC](https://discuss.elastic.co/t/multiple-elasticsearch-instances-architecture/333187 "2023-05-11T10:18:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jabulon](https://avatars.discourse-cdn.com/v4/letter/j/dc4da7/32.png) [@jabulon](https://discuss.elastic.co/u/jabulon)\
**Post date:** [May 11, 2023, 10:18am UTC](https://discuss.elastic.co/t/multiple-elasticsearch-instances-architecture/333187/1 "2023-05-11T10:18:53Z")

</div>

I am designing a solution based on many smaller Elasticsearch engines scattered around the world, and a single instance containing all of the data from all of the instances combined. I do not need the data to be up to date by the second, but do require eventual consistency in a minute or so.  
Each smaller instance is a single cluster with either 1 or two nodes.

What is the best approach? Should my central instance be a cluster and all the other smaller clusters sync their data into it? Is there such a feature: cluster of clusters?  
If this is not the best way, what are the alternatives?  
Should I perhaps use one of the Beats to push the data from each individual instance to the central one?

---

<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:** [June 8, 2023, 10:19am UTC](https://discuss.elastic.co/t/multiple-elasticsearch-instances-architecture/333187/2 "2023-06-08T10:19:24Z")

</div>

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