# Synchronisation strategies for ES 2

**URL:** <https://discuss.elastic.co/t/synchronisation-strategies-for-es-2/35500>\
**Category:** Elasticsearch\
**Created:** [November 25, 2015, 12:26am UTC](https://discuss.elastic.co/t/synchronisation-strategies-for-es-2/35500 "2015-11-25T00:26:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![snahor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/snahor/32/6145_2.png) [@snahor](https://discuss.elastic.co/u/snahor)\
**Post date:** [November 25, 2015, 12:26am UTC](https://discuss.elastic.co/t/synchronisation-strategies-for-es-2/35500/1 "2015-11-25T00:26:06Z")

</div>

Hey folks,

I was wondering what's the best strategy to keep the data synced in this new release. In the past, I've used the bulk api, or updated after committing to the main store. My current need is to have ES as synced as possible.

Thanks.

---

<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:** [November 25, 2015, 12:30am UTC](https://discuss.elastic.co/t/synchronisation-strategies-for-es-2/35500/2 "2015-11-25T00:30:09Z")

</div>

Why would the bulk API not be suitable in 2.0?

---

<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:36pm UTC](https://discuss.elastic.co/t/synchronisation-strategies-for-es-2/35500/3 "2017-07-05T23:36:10Z")

</div>

Closed on July 5, 2017, 11:36pm UTC