DEV Community

Node vs Go: Which one to choose for Backend development in 2022?

Harshal Suthar on July 29, 2022

What is Node? Node is an eminent JavaScript runtime environment that is often mistaken for a programming language. Node is used to creat...

Read full post

Ankush Thakur • Jul 29 '22

In my opinion, Node + TypeScript is so much mental baggage that you're better off using Go. HOWEVER, one shouldn't be blind to market realities. As such, we can "prefer" a technology stack, but we certainly don't get to "choose" one.

Eljay-Adobe • Jul 29 '22

"It possesses the speed of Python and the benefits of C."

lol

leob • Jul 30 '22

Yeah that should be kinda the other way around, lol ;)

Eljay-Adobe • Jul 30 '22

Reminds me of a quip I thought was funny...

Java elegantly combines all the disadvantages of a compiled programming language like C++, with all the disadvantages of a scripting language like Python, and none of the advantages of either.

(Note: I like Java. I like Python. I have a love-hate relationship with C++. For those who are Java fans, substitute C# for Java.)

leob • Jul 31 '22

I vaguely remember having heard that one before as well haha :)

Harshal Suthar • Aug 2 '22

I appreciate everyone's thoughts and opinions on the matter. However, as discussed above every language being great in their strengths, also have some weaknesses. This blog just provided a high-level overview of Node vs. GO. Finally, everyone has to choose the finest language that meets their company needs and offers value to their time investment.

Thank you for taking time to read our blog.

leob • Jul 30 '22

This article kinda obscures the fact that Go really runs rings around Node when it comes to performance (talking about highly scalable network apps) ...

Jacob Enders • Jul 29 '22

Node is not high performance. It's pretty slow compared to other solutions.

Haven't tried python though....

leob • Jul 30 '22

Read stories about companies running high scalability networking apps (think REST APIs and sockets and all that), and after converting their codebase from Node to Go they ended up needing one fifth or one tenth of the hardware to run it ...