# ElasticSearch push mechanism

**URL:** <https://discuss.elastic.co/t/elasticsearch-push-mechanism/27373>\
**Category:** Elasticsearch\
**Created:** [August 14, 2015, 7:00am UTC](https://discuss.elastic.co/t/elasticsearch-push-mechanism/27373 "2015-08-14T07:00:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ashish\_Mukherjee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ashish_mukherjee/32/4190_2.png) [@Ashish\_Mukherjee](https://discuss.elastic.co/u/Ashish_Mukherjee)\
**Post date:** [August 14, 2015, 7:00am UTC](https://discuss.elastic.co/t/elasticsearch-push-mechanism/27373/1 "2015-08-14T07:00:55Z")

</div>

Hello,

I have a scenario where my ElasticSearch index is being updated very frequently (nearly every second). I would like to implement a push-based mechanism to stream the latest data to the client (Browser). I was considering using Websockets for this.

I was looking at the ES Websocket plugin but it seems to have dependency on JBoss Netty etc. Is there anything different in writing a WebSocket server with javax.websocket , which performs a query to ES every n seconds (say, n = 3) and then writes the fresh data to the Web socket client?

Is there any more optimal approach to this?

Regards,  
Ashish

---

<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:55pm UTC](https://discuss.elastic.co/t/elasticsearch-push-mechanism/27373/2 "2017-07-05T23:55:51Z")

</div>