As stated, you only had 2 services in Node with the majority of your base being in Python, so saying ‘Making the Switch from Node.js to Golang’ is a bit misleading especially when you later go on to say that Python will always be a majority of the stack. Beyond that, you point out nothing defective about Node necessitating a switch to Go for this particular situation. In fact, all that has really happened here is just another day in the life of a developer. You tried to write something from scratch, spent a fair share of time on it and it didn’t work. You then found some code from an article you read which happened to be written in Go and basically did exactly the same thing you were trying to do. You solved the problem, and that’s all that really matters. This post, however, really just sounds like blaming the language and not the developer. I was waiting for the meat of the post that got into why Go worked over Node, but it didn’t happen. Why? Because you could have successfully implemented the exact same thing in Node, and had that Go code not existed I guarantee you would have as you were seemingly on the right track already. So, your first big module at your new gig failed…don’t pass blame. You might be using some Node code over Go when the situation is reversed. This reminds me of when I read TJ’s article about how he was dropping Node because Go was a better lover when in reality his jeans were just on too tight. You didn’t go the way of the gopher, you just went the way of code that worked. Having said all that, great job on solving the problem, but your title is simply clickbait.