# ZeroMQ transport layer plugin **URL:** \ **Category:** Elasticsearch\ **Created:** [October 28, 2011, 2:49pm UTC](https://discuss.elastic.co/t/zeromq-transport-layer-plugin/5717 "2011-10-28T14:49:21Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Tanguy1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy1/32/1749_2.png) [@Tanguy1](https://discuss.elastic.co/u/Tanguy1)\ **Post date:** [October 28, 2011, 2:49pm UTC](https://discuss.elastic.co/t/zeromq-transport-layer-plugin/5717/1 "2011-10-28T14:49:21Z")
Hi all, I don't know if you are interested in this, but I wrote a transport module that exposes the REST interface of ES over ZeroMQ. This way, it is possible to send REST-like messages with ØMQ clients and get the replies back. For example, a ØMQ client can send the following message: POST|/twitter/tweet/2|{"user": "kimchy","post\_date": "2009-11-15T14:12:12","message": "You know, for Search"} It will receive the following response: CREATED|{"ok":true,"\_index":"twitter","\_type":"tweet","\_id":"2","\_version":1} The transport layer converts ØMQ messages in a given format into REST request objects that can be handled by ES. The expected format for incoming messages is: \|\| But any other message format can be easely implemented. The SimpleClient class in test package shows how to create a simple ØMQ client and send messages. The implementation uses a router-dealer pattern ( [http://www.zeromq.org/sandbox:dealer](http://www.zeromq.org/sandbox:dealer)), where multiple XREP sockets are listening to incoming messages (each in a dedicated thread). The source code is located at [https://github.com/tlrx/elasticsearch/tree/master/plugins/transport/zeromq](https://github.com/tlrx/elasticsearch/tree/master/plugins/transport/zeromq) , I used the Thrift module as a good example. I still working on this (tests, benchmarks, distribute incoming messages on many ES nodes) but your feedback will be greatly appreciated. Thanks, -- Tanguy ---
**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\ **Post date:** [October 29, 2011, 2:32pm UTC](https://discuss.elastic.co/t/zeromq-transport-layer-plugin/5717/2 "2011-10-29T14:32:00Z")
Hiya Tanguy > I don't know if you are interested in this, but I wrote a transport > module that exposes the REST interface of ES over ZeroMQ. This way, it > is possible to send REST-like messages with ØMQ clients and get the > replies back. I'd be very interested in seeing this work. I tried to build ES from your branch with gradlew, but it complained of missing the jzmq dependency. Perhaps there is some missing config I need to get the build working correctly? Also, I've never actually used zeromq, just read the website a bit. Could you provide some client code demonstrating how it should be used? Your config specifies port 9700 and port 9800 - which one should the client talk to? thanks clint > For example, a ØMQ client can send the following message: > POST|/twitter/tweet/2|{"user": "kimchy","post\_date": > "2009-11-15T14:12:12","message": "You know, for Search"} > > It will receive the following response: > CREATED|{"ok":true,"\_index":"twitter","\_type":"tweet","\_id":"2","\_version":1} > > The transport layer converts ØMQ messages in a given format into REST > request objects that can be handled by ES. > > The expected format for incoming messages is: > \|\| > > But any other message format can be easely implemented. The > SimpleClient class in test package shows how to create a simple ØMQ > client and send messages. > > The implementation uses a router-dealer pattern > ([The ROUTER and DEALER - zeromq](http://www.zeromq.org/sandbox:dealer)), where multiple XREP sockets > are listening to incoming messages (each in a dedicated thread). > > The source code is located > at [https://github.com/tlrx/elasticsearch/tree/master/plugins/transport/zeromq](https://github.com/tlrx/elasticsearch/tree/master/plugins/transport/zeromq) , I used the Thrift module as a good example. > > I still working on this (tests, benchmarks, distribute incoming > messages on many ES nodes) but your feedback will be greatly > appreciated. > > Thanks, > > -- Tanguy ---
**Author:** ![Tanguy1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy1/32/1749_2.png) [@Tanguy1](https://discuss.elastic.co/u/Tanguy1)\ **Post date:** [October 31, 2011, 7:44am UTC](https://discuss.elastic.co/t/zeromq-transport-layer-plugin/5717/3 "2011-10-31T07:44:57Z")
Hi Clitnton, to build this plugin, you need to: 1. build ZeroMQ distribution v2.1 2. build ZeroMQ Java binding library (jzmq) 3. configure or add the library to your local gradle repository For step 1) and 2), I encourage you to read the procedure on the ZeroMQ web site, which is very well documented. From my experience, it will be easier on a Linux box. This thread from the ZeroMQ mailing list can also help you: [http://lists.zeromq.org/pipermail/zeromq-dev/2011-October/013762.html](http://lists.zeromq.org/pipermail/zeromq-dev/2011-October/013762.html) You can also build the jzmq library with Maven and install it in your local repo with mvn install. For step 3), I declared a maven local repository in the build.gradle file. This allow you to use your local maven rep to retrieve the jzmq-2.1.0-SNAPSHOT.jar file. Then, you can test the plugin with the SimpleClient file provided. Here is an example of the args you can provide to the SimpleClass: tcp://localhost:9700 PUT /twitter/tweet/2 "{... json content...}" External XREQ sockets must connect to plugin with the tcp://localhost:9700 address (can be configured in ES config file). The other address is used internally by the plugin. I updated the config file on github to avoid confusion. See u, -- Tanguy On 29 oct, 15:32, Clinton Gormley [cl...@traveljury.com](mailto:cl...@traveljury.com) wrote: > Hiya Tanguy > > > I don't know if you are interested in this, but I wrote a transport > > module that exposes the REST interface of ES over ZeroMQ. This way, it > > is possible to send REST-like messages with ØMQ clients and get the > > replies back. > > I'd be very interested in seeing this work. > > I tried to build ES from your branch with gradlew, but it complained of > missing the jzmq dependency. Perhaps there is some missing config I > need to get the build working correctly? > > Also, I've never actually used zeromq, just read the website a bit. > > Could you provide some client code demonstrating how it should be used? > > Your config specifies port 9700 and port 9800 - which one should the > client talk to? > > thanks > > clint > > > For example, a ØMQ client can send the following message: > > POST|/twitter/tweet/2|{"user": "kimchy","post\_date": > > "2009-11-15T14:12:12","message": "You know, for Search"} > > > It will receive the following response: > > CREATED|{"ok":true,"\_index":"twitter","\_type":"tweet","\_id":"2","\_version": 1} > > > The transport layer converts ØMQ messages in a given format into REST > > request objects that can be handled by ES. > > > The expected format for incoming messages is: > > \|\| > > > But any other message format can be easely implemented. The > > SimpleClient class in test package shows how to create a simple ØMQ > > client and send messages. > > > The implementation uses a router-dealer pattern > > ([The ROUTER and DEALER - zeromq](http://www.zeromq.org/sandbox:dealer)), where multiple XREP sockets > > are listening to incoming messages (each in a dedicated thread). > > > The source code is located > > athttps://github.com/tlrx/elasticsearch/tree/master/plugins/transport/z..., I used the Thrift module as a good example. > > > I still working on this (tests, benchmarks, distribute incoming > > messages on many ES nodes) but your feedback will be greatly > > appreciated. > > > Thanks, > > > -- Tanguy ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 31, 2011, 5:11pm UTC](https://discuss.elastic.co/t/zeromq-transport-layer-plugin/5717/4 "2011-10-31T17:11:07Z")
Hey, Thanks for this!. I was dabbling with zeromq a bit, but never had proper time to actually use it. Is there a chance that you can move it into a completely separate plugin, not a fork of elasticsearch? On Fri, Oct 28, 2011 at 4:49 PM, tlrx [tlrx.dev@gmail.com](mailto:tlrx.dev@gmail.com) wrote: > Hi all, > > I don't know if you are interested in this, but I wrote a transport module > that exposes the REST interface of ES over ZeroMQ. This way, it is possible > to send REST-like messages with ØMQ clients and get the replies back. > > For example, a ØMQ client can send the following message: > > POST|/twitter/tweet/2|{"user": "kimchy","post\_date": > "2009-11-15T14:12:12","message": "You know, for Search"} > > It will receive the following response: > > CREATED|{"ok":true,"\_index":"twitter","\_type":"tweet","\_id":"2","\_version":1} > > The transport layer converts ØMQ messages in a given format into REST > request objects that can be handled by ES. > > The expected format for incoming messages is: > > \|\| > > But any other message format can be easely implemented. The SimpleClient > class in test package shows how to create a simple ØMQ client and send > messages. > > The implementation uses a router-dealer pattern ( > [The ROUTER and DEALER - zeromq](http://www.zeromq.org/sandbox:dealer)), where multiple XREP sockets are > listening to incoming messages (each in a dedicated thread). > > The source code is located at > [https://github.com/tlrx/elasticsearch/tree/master/plugins/transport/zeromq](https://github.com/tlrx/elasticsearch/tree/master/plugins/transport/zeromq) , > I used the Thrift module as a good example. > > I still working on this (tests, benchmarks, distribute incoming messages > on many ES nodes) but your feedback will be greatly appreciated. > > Thanks, > > -- Tanguy ---
**Author:** ![Tanguy\_Leroux](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy_leroux/32/121066_2.png) [@Tanguy\_Leroux](https://discuss.elastic.co/u/Tanguy_Leroux)\ **Post date:** [November 1, 2011, 3:53pm UTC](https://discuss.elastic.co/t/zeromq-transport-layer-plugin/5717/5 "2011-11-01T15:53:35Z")
Hi Shay, It was a pleasure to code it 🙂 I forked ES since it was easier to developp and debug the code, but I can move it in a separate plugin. Do you have an example on github? I will do this next week, I think. And write some doc. -- Tanguy On 31 oct, 18:11, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > Hey, > > Thanks for this!. I was dabbling with zeromq a bit, but never had proper > time to actually use it. Is there a chance that you can move it into a > completely separate plugin, not a fork of elasticsearch? > > On Fri, Oct 28, 2011 at 4:49 PM, tlrx [tlrx....@gmail.com](mailto:tlrx....@gmail.com) wrote: > > > Hi all, > > > I don't know if you are interested in this, but I wrote a transport module > > that exposes the REST interface of ES over ZeroMQ. This way, it is possible > > to send REST-like messages with ØMQ clients and get the replies back. > > > For example, a ØMQ client can send the following message: > > > POST|/twitter/tweet/2|{"user": "kimchy","post\_date": > > "2009-11-15T14:12:12","message": "You know, for Search"} > > > It will receive the following response: > > > CREATED|{"ok":true,"\_index":"twitter","\_type":"tweet","\_id":"2","\_version": 1} > > > The transport layer converts ØMQ messages in a given format into REST > > request objects that can be handled by ES. > > > The expected format for incoming messages is: > > > \|\| > > > But any other message format can be easely implemented. The SimpleClient > > class in test package shows how to create a simple ØMQ client and send > > messages. > > > The implementation uses a router-dealer pattern ( > > [The ROUTER and DEALER - zeromq](http://www.zeromq.org/sandbox:dealer)), where multiple XREP sockets are > > listening to incoming messages (each in a dedicated thread). > > > The source code is located at > > [https://github.com/tlrx/elasticsearch/tree/master/plugins/transport/z](https://github.com/tlrx/elasticsearch/tree/master/plugins/transport/z)..., > > I used the Thrift module as a good example. > > > I still working on this (tests, benchmarks, distribute incoming messages > > on many ES nodes) but your feedback will be greatly appreciated. > > > Thanks, > > > -- Tanguy ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [November 1, 2011, 6:09pm UTC](https://discuss.elastic.co/t/zeromq-transport-layer-plugin/5717/6 "2011-11-01T18:09:07Z")
The RSS river is one example of a standalone plugin: [GitHub - dadoonet/rssriver: Elasticsearch Rss River (PROJECT STOPPED)](https://github.com/dadoonet/rssriver). On Tue, Nov 1, 2011 at 5:53 PM, tlrx [tanguy.leroux@gmail.com](mailto:tanguy.leroux@gmail.com) wrote: > Hi Shay, > > It was a pleasure to code it 🙂 I forked ES since it was easier to > developp and debug the code, but I can move it in a separate plugin. > > Do you have an example on github? > > I will do this next week, I think. And write some doc. > > -- Tanguy > > On 31 oct, 18:11, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > Hey, > > > > Thanks for this!. I was dabbling with zeromq a bit, but never had > > proper > > time to actually use it. Is there a chance that you can move it into a > > completely separate plugin, not a fork of elasticsearch? > > > > On Fri, Oct 28, 2011 at 4:49 PM, tlrx [tlrx....@gmail.com](mailto:tlrx....@gmail.com) wrote: > > > > > Hi all, > > > > > I don't know if you are interested in this, but I wrote a transport > > > module > > > that exposes the REST interface of ES over ZeroMQ. This way, it is > > > possible > > > to send REST-like messages with ØMQ clients and get the replies back. > > > > > For example, a ØMQ client can send the following message: > > > > > POST|/twitter/tweet/2|{"user": "kimchy","post\_date": > > > "2009-11-15T14:12:12","message": "You know, for Search"} > > > > > It will receive the following response: > > > > > > > CREATED|{"ok":true,"\_index":"twitter","\_type":"tweet","\_id":"2","\_version": > 1} > > > > The transport layer converts ØMQ messages in a given format into REST > > > request objects that can be handled by ES. > > > > > The expected format for incoming messages is: > > > > > \|\| > > > > > But any other message format can be easely implemented. The > > > SimpleClient > > > class in test package shows how to create a simple ØMQ client and send > > > messages. > > > > > The implementation uses a router-dealer pattern ( > > > [The ROUTER and DEALER - zeromq](http://www.zeromq.org/sandbox:dealer)), where multiple XREP sockets are > > > listening to incoming messages (each in a dedicated thread). > > > > > The source code is located at > > > [https://github.com/tlrx/elasticsearch/tree/master/plugins/transport/z](https://github.com/tlrx/elasticsearch/tree/master/plugins/transport/z).. > > > ., > > > I used the Thrift module as a good example. > > > > > I still working on this (tests, benchmarks, distribute incoming > > > messages > > > on many ES nodes) but your feedback will be greatly appreciated. > > > > > Thanks, > > > > > -- Tanguy ---
**Author:** ![Tanguy1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy1/32/1749_2.png) [@Tanguy1](https://discuss.elastic.co/u/Tanguy1)\ **Post date:** [November 5, 2011, 4:19pm UTC](https://discuss.elastic.co/t/zeromq-transport-layer-plugin/5717/7 "2011-11-05T16:19:30Z")
Hi Shay, I moved the code to a separate plugin: [GitHub - tlrx/transport-zeromq: ØMQ transport layer plugin for Elasticsearch](https://github.com/tlrx/transport-zeromq) Now it can be installed with Elasticsearch plugin script. I also write some documentation, inspired by the RSS river. I still working on this plugin, but feedback will be appreciated :o) -- Tanguy On 1 nov, 19:09, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > The RSS river is one example of a standalone plugin:[GitHub - dadoonet/rssriver: Elasticsearch Rss River (PROJECT STOPPED)](https://github.com/dadoonet/rssriver). > > On Tue, Nov 1, 2011 at 5:53 PM, tlrx [tanguy.ler...@gmail.com](mailto:tanguy.ler...@gmail.com) wrote: > > > Hi Shay, > > > It was a pleasure to code it 🙂 I forked ES since it was easier to > > developp and debug the code, but I can move it in a separate plugin. > > > Do you have an example on github? > > > I will do this next week, I think. And write some doc. > > > -- Tanguy > > > On 31 oct, 18:11, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > > > Hey, > > > > Thanks for this!. I was dabbling with zeromq a bit, but never had > > > proper > > > time to actually use it. Is there a chance that you can move it into a > > > completely separate plugin, not a fork of elasticsearch? > > > > On Fri, Oct 28, 2011 at 4:49 PM, tlrx [tlrx....@gmail.com](mailto:tlrx....@gmail.com) wrote: > > > > > > > Hi all, > > > > > I don't know if you are interested in this, but I wrote a transport > > > > module > > > > that exposes the REST interface of ES over ZeroMQ. This way, it is > > > > possible > > > > to send REST-like messages with ØMQ clients and get the replies back. > > > > > For example, a ØMQ client can send the following message: > > > > > POST|/twitter/tweet/2|{"user": "kimchy","post\_date": > > > > "2009-11-15T14:12:12","message": "You know, for Search"} > > > > > It will receive the following response: > > > CREATED|{"ok":true,"\_index":"twitter","\_type":"tweet","\_id":"2","\_version": > > 1} > > > > > The transport layer converts ØMQ messages in a given format into REST > > > > request objects that can be handled by ES. > > > > > The expected format for incoming messages is: > > > > > \|\| > > > > > But any other message format can be easely implemented. The > > > > SimpleClient > > > > class in test package shows how to create a simple ØMQ client and send > > > > messages. > > > > > The implementation uses a router-dealer pattern ( > > > > [The ROUTER and DEALER - zeromq](http://www.zeromq.org/sandbox:dealer)), where multiple XREP sockets are > > > > listening to incoming messages (each in a dedicated thread). > > > > > The source code is located at > > > > [https://github.com/tlrx/elasticsearch/tree/master/plugins/transport/z](https://github.com/tlrx/elasticsearch/tree/master/plugins/transport/z).. > > > > ., > > > > I used the Thrift module as a good example. > > > > > I still working on this (tests, benchmarks, distribute incoming > > > > messages > > > > on many ES nodes) but your feedback will be greatly appreciated. > > > > > Thanks, > > > > > -- Tanguy ---
**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\ **Post date:** [November 6, 2011, 1:58pm UTC](https://discuss.elastic.co/t/zeromq-transport-layer-plugin/5717/8 "2011-11-06T13:58:46Z")
> I moved the code to a separate plugin: [GitHub - tlrx/transport-zeromq: ØMQ transport layer plugin for Elasticsearch](https://github.com/tlrx/transport-zeromq) ++ for the improved docs 🙂 clint > Now it can be installed with Elasticsearch plugin script. I also write > some documentation, inspired by the RSS river. > > I still working on this plugin, but feedback will be appreciated :o) > > -- Tanguy > > On 1 nov, 19:09, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > The RSS river is one example of a standalone plugin:[GitHub - dadoonet/rssriver: Elasticsearch Rss River (PROJECT STOPPED)](https://github.com/dadoonet/rssriver). > > > > On Tue, Nov 1, 2011 at 5:53 PM, tlrx [tanguy.ler...@gmail.com](mailto:tanguy.ler...@gmail.com) wrote: > > > > > Hi Shay, > > > > > It was a pleasure to code it 🙂 I forked ES since it was easier to > > > developp and debug the code, but I can move it in a separate plugin. > > > > > Do you have an example on github? > > > > > I will do this next week, I think. And write some doc. > > > > > -- Tanguy > > > > > On 31 oct, 18:11, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > > > > > Hey, > > > > > > Thanks for this!. I was dabbling with zeromq a bit, but never had > > > > proper > > > > time to actually use it. Is there a chance that you can move it into a > > > > completely separate plugin, not a fork of elasticsearch? > > > > > > On Fri, Oct 28, 2011 at 4:49 PM, tlrx [tlrx....@gmail.com](mailto:tlrx....@gmail.com) wrote: > > > > > > > > > Hi all, > > > > > > > I don't know if you are interested in this, but I wrote a transport > > > > > module > > > > > that exposes the REST interface of ES over ZeroMQ. This way, it is > > > > > possible > > > > > to send REST-like messages with ØMQ clients and get the replies back. > > > > > > > For example, a ØMQ client can send the following message: > > > > > > > POST|/twitter/tweet/2|{"user": "kimchy","post\_date": > > > > > "2009-11-15T14:12:12","message": "You know, for Search"} > > > > > > > It will receive the following response: > > > > > CREATED|{"ok":true,"\_index":"twitter","\_type":"tweet","\_id":"2","\_version": > > > 1} > > > > > > > The transport layer converts ØMQ messages in a given format into REST > > > > > request objects that can be handled by ES. > > > > > > > The expected format for incoming messages is: > > > > > > > \|\| > > > > > > > But any other message format can be easely implemented. The > > > > > SimpleClient > > > > > class in test package shows how to create a simple ØMQ client and send > > > > > messages. > > > > > > > The implementation uses a router-dealer pattern ( > > > > > [The ROUTER and DEALER - zeromq](http://www.zeromq.org/sandbox:dealer)), where multiple XREP sockets are > > > > > listening to incoming messages (each in a dedicated thread). > > > > > > > The source code is located at > > > > > [https://github.com/tlrx/elasticsearch/tree/master/plugins/transport/z](https://github.com/tlrx/elasticsearch/tree/master/plugins/transport/z).. > > > > > ., > > > > > I used the Thrift module as a good example. > > > > > > > I still working on this (tests, benchmarks, distribute incoming > > > > > messages > > > > > on many ES nodes) but your feedback will be greatly appreciated. > > > > > > > Thanks, > > > > > > > -- Tanguy ---
**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\ **Post date:** [November 6, 2011, 5:40pm UTC](https://discuss.elastic.co/t/zeromq-transport-layer-plugin/5717/9 "2011-11-06T17:40:58Z")
Hi Tanguy On Sun, Nov 6, 2011 at 2:58 PM, Clinton Gormley [clint@traveljury.com](mailto:clint@traveljury.com)wrote: > > I moved the code to a separate plugin: > > [GitHub - tlrx/transport-zeromq: ØMQ transport layer plugin for Elasticsearch](https://github.com/tlrx/transport-zeromq) OK - i managed to get a Perl script talking to Elasticsearch via ZeroMQ I've played with it very briefly, and opened 2 issues for bugs: > **[Issues · tlrx/transport-zeromq](https://github.com/tlrx/transport-zeromq/issues)** > > ØMQ transport layer plugin for Elasticsearch. Contribute to tlrx/transport-zeromq development by creating an account on GitHub. Looking forward to seeing this plugin become solid! clint ---
**Author:** ![Tanguy\_Leroux](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy_leroux/32/121066_2.png) [@Tanguy\_Leroux](https://discuss.elastic.co/u/Tanguy_Leroux)\ **Post date:** [November 7, 2011, 8:06am UTC](https://discuss.elastic.co/t/zeromq-transport-layer-plugin/5717/10 "2011-11-07T08:06:55Z")
Thanks for your feedback, Clint. I'll work on it as soon as possible 🙂 On Nov 6, 6:40 pm, Clinton Gormley [cl...@traveljury.com](mailto:cl...@traveljury.com) wrote: > Hi Tanguy > > On Sun, Nov 6, 2011 at 2:58 PM, Clinton Gormley [cl...@traveljury.com](mailto:cl...@traveljury.com)wrote: > > > > I moved the code to a separate plugin: > > > [GitHub - tlrx/transport-zeromq: ØMQ transport layer plugin for Elasticsearch](https://github.com/tlrx/transport-zeromq) > > OK - i managed to get a Perl script talking to Elasticsearch via ZeroMQ > > I've played with it very briefly, and opened 2 issues for bugs:[Issues · tlrx/transport-zeromq · GitHub](https://github.com/tlrx/transport-zeromq/issues) > > Looking forward to seeing this plugin become solid! > > clint ---
**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, 3:49am UTC](https://discuss.elastic.co/t/zeromq-transport-layer-plugin/5717/11 "2017-07-06T03:49:49Z")