Go vs Node.js for GraphQL endpoint

<p>As part of my master&#39;s thesis I have to integrate/unify multiple REST endpoints for an IoT-Cloud we&#39;re building with GraphQL and build a framework/set of rules for further development with GraphQL. As part of that I have to <em>somehow</em> evaluate which programming language to choose given Node.js, Spring Boot and Go. I kicked Spring Boot due to its meh compatibility when it comes to GraphQL and further development. </p> <p>So since his subreddit seems to be kinda active and people are able to reflect critically, I came here to ask as part of my conducted study^{that consists of internet posts...}: Does GraphQL benefit of Go&#39;s scalability and performance? Which of the languages would you use given the task at hand?</p> <hr/>**评论：**<br/><br/>philiplb: <pre><p>Currently, we are using <a href="https://github.com/graphql-go/graphql" rel="nofollow">https://github.com/graphql-go/graphql</a> for a project. So far: - Working good - Documentation non existant - But some examples are there - Only drawback so far: The GraphQL-Error-Object is not customizable as far as I can see. You can just set an error string.</p></pre>Teilchen: <pre><p>Thank you! What did you base your decision of going with GraphQL &amp; Go on?</p></pre>philiplb: <pre><p>I wanted to do this project in Go and I wanted to give GraphQL a try. Last thing was to choose the library: The one mentioned above is under active development, is widespread, has many Github-Stars. So I gave it a try and so far it works for me. :) For performance, this issue is interesting: <a href="https://github.com/graphql-go/graphql/issues/119" rel="nofollow">https://github.com/graphql-go/graphql/issues/119</a> Bottomline: This library isn&#39;t optimized (yet) but already achives competitive performance.</p></pre>shark1337: <pre><p>playlyfe/graphql claims to be x10 faster than node js graphql. I&#39;ve been using both and can see that using graphql with go seemed a little easier to me, but that&#39;s just me ;)</p></pre>Teilchen: <pre><p>Good point! Thought about this too and found <a href="https://github.com/graphql-go/graphql/issues/119" rel="nofollow">this benchmark</a> that showed Go was slightly faster than Node.js and failed less overall.<br/> The question that comes to mind tho is - what is this speed advantage good for, if say a REST or database call is the limiter, slowing down the whole operation?</p></pre>wittywitwitty: <pre><p>I would assume that the speed advantage would affect hardware decisions and overhead if you want to think that far out. Faster performance can have a positive impact on available resources.</p></pre>philiplb: <pre><p>I looked at this one, too but for a production system it seemed too young. But promising. :)</p></pre>Zamicol: <pre><p><a href="https://github.com/playlyfe/go-graphql" rel="nofollow">https://github.com/playlyfe/go-graphql</a></p></pre>