4 ms·
I picked Go because it tends to use fewer resources than Node.js, and startup time is quite fast.
by clintonb 4mo ago
I picked Go because it tends to use fewer resources than Node.js, and startup time is quite fast.
- hirvi74 4mo agoI've never used Node, so I can't judge it. I'm still stuck in the C# world. So, I am curious how Go performs in comparison. I'll need to do some research. Though, it was a slap in the face for a lot of C#-ers when Go beat out C# for the Typescript compiler rewrite. I personally do not mind because C# is my Enterprise language, but it's not my favorite language or anything.
- clintonb 4mo agoI don’t have any head-to-head comparisons of the same app written in both languages. I can compare apps with similar functionality: listening to GitHub web hooks vs. Linear web hooks. Both are deployed to Kubernetes. The GitHub listener written in Go has a CPU limit of 50m, but actual usage of 10m. Memory consumption is around 34MB of a 64MB limit. The Linear listener written in Typescript consumes around 20m/250m CPU, but 235MB/500MB memory. The 2x CPU and 9-10x memory consumption is significant, especially as we scale usage or add services. (Yes, I know we need to do more right-sizing.)