# Geographic data vs data location

**URL:** <https://discuss.elastic.co/t/geographic-data-vs-data-location/3328>\
**Category:** Elasticsearch\
**Created:** [September 13, 2010, 7:00am UTC](https://discuss.elastic.co/t/geographic-data-vs-data-location/3328 "2010-09-13T07:00:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gearond](https://avatars.discourse-cdn.com/v4/letter/g/e68b1a/32.png) [@gearond](https://discuss.elastic.co/u/gearond)\
**Post date:** [September 13, 2010, 7:00am UTC](https://discuss.elastic.co/t/geographic-data-vs-data-location/3328/1 "2010-09-13T07:00:32Z")

</div>

Think about THE big one - google.

(First, China for this example is avoided because much Chinese data is ILLEGAL to be  
provided for search outside of China)

If there is data generated by people in Europe, in various languages:  
1/ Is it stored close to where it is generated?  
2/ Are sharding and replicatiion also close to where it is generated?  
3/ How accessible IS that data to someone from the US who speaks one of those languages?  
4/ How much is sharding and replication done AWAY from where data is geographically generated?

What are people's thoughts on making sites that cater to people interested in web pages, etc in other countries? Any examples out there?

---

<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 6, 2017, 4:19am UTC](https://discuss.elastic.co/t/geographic-data-vs-data-location/3328/2 "2017-07-06T04:19:25Z")

</div>

Closed on July 6, 2017, 4:19am UTC


