If it's consuming static data from DB, Node.js + GraphQL indeed would be better than .NET Core + GraphQL (on paper).
But, what about non-static data GraphQL API? Maybe you can manage some data processing directly from the DB but I truly don't know if this is a good practice for everything I don't think it's possible to handle everything on it.
In fact, I'm working on a project where back-end would be a .NET Core + GraphQL API and front-end would be a React app with a simple Node.js server (express) for the requests.
I think it would be fun to build both options to compare performance but I need to figure out what tasks I would code to make back-end work hard processing data.
If it's consuming static data from DB, Node.js + GraphQL indeed would be better than .NET Core + GraphQL (on paper).
But, what about non-static data GraphQL API? Maybe you can manage some data processing directly from the DB but I truly don't know if this is a good practice for everything I don't think it's possible to handle everything on it.
In fact, I'm working on a project where back-end would be a .NET Core + GraphQL API and front-end would be a React app with a simple Node.js server (express) for the requests.
I think it would be fun to build both options to compare performance but I need to figure out what tasks I would code to make back-end work hard processing data.
Great :)
I wish you all the best with your current project :) and of course waiting your nice Feedback!
Thanks a lot Manuel :)