What are the advantages for companies to use both Go and Nodejs on the backend?

<p>I would like to know if companies tend to always only use Go or Node.js as backend solution for their server or in some cases it is useful to use both.</p> <hr/>**评论：**<br/><br/>titpetric: <pre><p>I&#39;m using node for services that already exist and might be considered good enough to use. Generally it&#39;s useful to use existing prior work in any language if it saves dev time and time to market. From what I&#39;ve seen, people are pretty exclusive as to what kind of stack they use (for obvious reasons), but there are complementary/equivalent implementations of some stuff in both languages. For example, if you want an image processing library, you have <a href="https://github.com/h2non/bimg" rel="nofollow">bimg</a> in Go, and <a href="https://github.com/lovell/sharp" rel="nofollow">sharp</a> in Node, and they are pretty much equivalent. In the end it&#39;s mostly the case of whatever language is more comfortable for the devs you manage to attract.</p> <p>I really use Node only for some tooling where it&#39;s untyped nature becomes an advantage. Somewhat. Most of the time, Go outperforms Node by a wide margin for any kind of network service which I&#39;ve implemented in both languages, so considering that Node is single threaded and you have to bolt-on process management and scaling, I&#39;ve just stopped developing back-end stuff with Node. I can&#39;t say it&#39;s not worth it, it just becomes obsolete as soon as you know enough Go to write even the simplest JSON API.</p></pre>shark1337: <pre><p>The old company that I&#39;ve worked for used to use c# for the API and node js for the rest (sessions, serving static files etc). Also, I&#39;m planning to run in production with a go API and probably some crystal, even though I&#39;ve good experience with node, won&#39;t trade native code for a scripted language..</p></pre>