# Geo-replication techniques? **URL:** \ **Category:** Elasticsearch\ **Created:** [January 15, 2016, 7:22pm UTC](https://discuss.elastic.co/t/geo-replication-techniques/39355 "2016-01-15T19:22:08Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![krzjez](https://avatars.discourse-cdn.com/v4/letter/k/e8c25b/32.png) [@krzjez](https://discuss.elastic.co/u/krzjez)\ **Post date:** [January 15, 2016, 7:22pm UTC](https://discuss.elastic.co/t/geo-replication-techniques/39355/1 "2016-01-15T19:22:08Z")
From what I understand ElasticSearch does not offer any features to do geo-replication. How are people addressing this issue for continuous data feed to ElasticSearch, async, with say 10s delay? I had a 1 year long break from ElasticSearch. I remember there were some talks about Tribes. Some possibilities I can think of: - Populate ES cluster at each location separately from some geo-replicated queue? - Tail and replicate transaction log (Translog) – is it possible, how? - River? - Snapshot? - Can I use Tribes for this? - Other? What is recommended or works in production? KJ ---
**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:** [January 16, 2016, 1:14am UTC](https://discuss.elastic.co/t/geo-replication-techniques/39355/2 "2016-01-16T01:14:53Z")
Check out [https://www.elastic.co/blog/scaling\_elasticsearch\_across\_data\_centers\_with\_kafka](https://www.elastic.co/blog/scaling_elasticsearch_across_data_centers_with_kafka) ---
**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:23pm UTC](https://discuss.elastic.co/t/geo-replication-techniques/39355/3 "2017-07-05T23:23:53Z")