# Sizing Architecture for Huge amount data

**URL:** <https://discuss.elastic.co/t/sizing-architecture-for-huge-amount-data/78837>\
**Category:** Elasticsearch\
**Created:** [March 16, 2017, 10:45am UTC](https://discuss.elastic.co/t/sizing-architecture-for-huge-amount-data/78837 "2017-03-16T10:45:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [March 16, 2017, 12:22pm UTC](https://discuss.elastic.co/t/sizing-architecture-for-huge-amount-data/78837/2 "2017-03-16T12:22:47Z")

</div>

It depends a lot on your data and requirements, so it is very hard to give any general recommendations. Please have a look at this [related thread](https://discuss.elastic.co/t/data-storage-estimation-for-es-cluster/77997).

---

_[View the full topic](https://discuss.elastic.co/t/sizing-architecture-for-huge-amount-data/78837)._