By David Baldwin Jan26 6:23:59 PM
Before Node.js popped on the scene, async was something (primarily) used by OS developers - backend web devs had few (easy) options to implement async functionality into their code. But then Node.js came on the scene in 2009 and took the web development community (as well as networking devs) by storm. Since then Node.js has been the go to technology for web apps needing high throughput and multiple sockets (e.g. web messaging).
However in 2012 all changed with the first stable release of Golang ; a open-sourced google backed language built with async and speed. Golang, invented at Google by Robert Griesemer, Rob Pike, and Ken Thompson is a statically typed language that closely resembles C; but with useful features like type-safety, non-blocking io, dynamic typing and with fast compilation times.
Let's look the disadvantages and advantages of each stack and see how they addup in the 'real world':
Since this site primarily deals web technologies, we'll narrow our focus to just backend web development ( and leave out the limitless other types of applications we could build).
First off Golang and NodeJS share similar features and technologies that power them. Both feature non-blocking io and are have dynamically cast types (no more type casting problems like C!)
Both also havefully featured standard libraries that support a multitude of functionalities, including HTTP and TCP (which can be access through interfaces in Go and modules in NodeJS).
OK. Thats great but your here to see which one is better right? Well then take a look below for the advantages and disadvantages:
As seen below in the test results by Jonathan Warner done here , Golang can now be considered a viable alternative to NodeJS. In his bubble sort and http tests, Golang came out on top. However it is to be noted that Go does randomly spike when handling plain HTTP requests compared to NodeJS, maknig me doubtfull on the scalability of these results.
|Avg of 5 trials||430ms||326.26ms|
However when the two techologies were subjected to a Redis bottleneck simulation, their performance gap siginficantly narrowed, making the difference between the two almost negligiable, as seen in the graph below (again done by Jonathan):
In summary I think its fair to say that at this point, what framework you use won't adversely affect your web app's performance. It really just comes down to whether you are willing to jump on a new technology before it is proven, or stay on the NodeJS train until you are comfortable. If you do want to code in Golang, take a look at this for more info.