# Node.JS client driver for DGraph?

**URL:** <https://discuss.dgraph.io/t/node-js-client-driver-for-dgraph/1116>\
**Category:** Users\
**Created:** [November 28, 2016, 6:30pm UTC](https://discuss.dgraph.io/t/node-js-client-driver-for-dgraph/1116 "2016-11-28T18:30:10Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![pmualaba](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/pmualaba/32/1035_2.png) [@pmualaba](https://discuss.dgraph.io/u/pmualaba)\
**Post date:** [November 28, 2016, 6:30pm UTC](https://discuss.dgraph.io/t/node-js-client-driver-for-dgraph/1116/1 "2016-11-28T18:30:10Z")

</div>

Are there any plans or progress in development of a Node.JS Language Driver? Since JavaScript is the language of the web and many developers are switching to Node.JS it would by great if we could access DGraph from Node.JS using JavaScript…

Any movement on this?

Patrick

---

<div class="post-metadata">

**Author:** ![mrjn](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/mrjn/32/775_2.png) [@mrjn](https://discuss.dgraph.io/u/mrjn)\
**Post date:** [November 29, 2016, 12:41am UTC](https://discuss.dgraph.io/t/node-js-client-driver-for-dgraph/1116/2 "2016-11-29T00:41:09Z")

</div>

Hey @pmualaba,

So, we have a `/query` endpoint, which is what we use from our Javascript. It takes GraphQL and outputs JSON.

Would that not work with Node.js?

---

<div class="post-metadata">

**Author:** ![pmualaba](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/pmualaba/32/1035_2.png) [@pmualaba](https://discuss.dgraph.io/u/pmualaba)\
**Post date:** [December 6, 2016, 7:27am UTC](https://discuss.dgraph.io/t/node-js-client-driver-for-dgraph/1116/3 "2016-12-06T07:27:08Z")

</div>

Sure, i will try that once 0.7 is released. could you please release a 0.7 docker image as well?

Thanks!

---

<div class="post-metadata">

**Author:** ![pmualaba](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/pmualaba/32/1035_2.png) [@pmualaba](https://discuss.dgraph.io/u/pmualaba)\
**Post date:** [January 30, 2017, 8:59am UTC](https://discuss.dgraph.io/t/node-js-client-driver-for-dgraph/1116/4 "2017-01-30T08:59:30Z")

</div>

Would the **/query** endpoint have a performance penalty over a dedicated **grpc** native client library for Node.JS?

---

<div class="post-metadata">

**Author:** ![mrjn](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/mrjn/32/775_2.png) [@mrjn](https://discuss.dgraph.io/u/mrjn)\
**Post date:** [January 30, 2017, 10:23pm UTC](https://discuss.dgraph.io/t/node-js-client-driver-for-dgraph/1116/5 "2017-01-30T22:23:52Z")

</div>

We have optimized our Json output. Also, the output is more readily consumable via JavaScript. So, I’d recommend using it, and if you feel the performance isn’t that good, you can switch to grpc.

I haven’t checked, but if there’s a way to keep http connections alive, we could look into it.

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex007/uploads/dgraph/original/2X/2/2b38fdece2abe5814f2e51bee69d1e67fc304b0a.png) [@system](https://discuss.dgraph.io/u/system)\
**Post date:** [November 28, 2017, 1:00am UTC](https://discuss.dgraph.io/t/node-js-client-driver-for-dgraph/1116/6 "2017-11-28T01:00:29Z")

</div>

Closed on November 28, 2017, 1:00am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.