golang-graphql-benchmark VS golang-for-nodejs-developers

I would argue that single threaded node is the bottleneck: imagine you have 4 processors and 4 node processes, and each process ties to handle requests in a most effective: process first request, while accessing file or db it start processing another request. The libs, in contrary, written in a bad way is the main bottleneck, and it's easy to prove: here is a benchmark of go graphql implementations (testing simple hello world): https://github.com/appleboy/golang-graphql-benchmark graphql-go - 19k rps gqlgen + net/http - 52k rps - 2.5 times faster

Have you ever tried gqlgen? I really enjoy the dev experience. It also looks like it has great benchmarks.

Fiber is fast and resembles the Node.js express framework, making it easier for a Node.js developer to transition to using Go. The complete code discussed in this article can be found in this repo.

To me makes sense what you are planning to do. You can start by having a look at this. Be careful about your mindset and you will be fine.

🌐 Note: Also, I recommend visiting the GitHub repository by Miguel Mota called Golang for Node.js Developers. It describes the basic principles for a smoother transition of your backend from JavaScript to Go in a fairly straightforward way.

Lol, after deeper looking at that better benchmark I see they measure "hello world" :) https://github.com/miguelmota/golang-for-nodejs-developers here I found Graphql benchmark

https://github.com/miguelmota/golang-for-nodejs-developers#examples