# Service layer on top of elasticsearch

**URL:** <https://discuss.elastic.co/t/service-layer-on-top-of-elasticsearch/1529>\
**Category:** Elasticsearch\
**Created:** [May 29, 2015, 12:21am UTC](https://discuss.elastic.co/t/service-layer-on-top-of-elasticsearch/1529 "2015-05-29T00:21:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![waater](https://avatars.discourse-cdn.com/v4/letter/w/5f9b8f/32.png) [@waater](https://discuss.elastic.co/u/waater)\
**Post date:** [May 29, 2015, 12:21am UTC](https://discuss.elastic.co/t/service-layer-on-top-of-elasticsearch/1529/1 "2015-05-29T00:21:19Z")

</div>

We are on our ideation for developing a service layer on top of our elasticsearch nodes for multiple services that will query the nodes. We have come down to using either Nodejs or Python clients.

I dont think there is a clear winner like any dev choice. How should we go about choosing one when I/Os performance and caching opportunities are high on our list. Asking this questions to get clarity on several libraries available in both python and nodejs that would suit elasticsearch IO.

---

<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:** [May 29, 2015, 2:18am UTC](https://discuss.elastic.co/t/service-layer-on-top-of-elasticsearch/1529/2 "2015-05-29T02:18:00Z")

</div>

Test.  
Test using data and queries that you expect to be processing on nodes with the same specs you are planning on using.

---

<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, 12:11am UTC](https://discuss.elastic.co/t/service-layer-on-top-of-elasticsearch/1529/3 "2017-07-06T00:11:04Z")

</div>

Closed on July 6, 2017, 12:11am UTC