Node.js has incredible performance for I/O apps and I think that it's easier to start with if you are a front-end dev (with experience using JS, of course).
Nonetheless, .NET Core is a better option if you want to set up a web API.
I would make an app in React (PWA) with a light back-end in Node.js just for parsing responses from an ASP.NET Core Web API.
Maybe, .NET Core will end the reign of Java in the "back-end world", but JavaScript is part of the web standard.
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.
Could you please share with us a link about how to build Node.js for parsing responses from ASP.Net core web api and what is the benefit from using this technique :) .
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Happy New Year, Ahmed.
Node.js has incredible performance for I/O apps and I think that it's easier to start with if you are a front-end dev (with experience using JS, of course).
Nonetheless, .NET Core is a better option if you want to set up a web API.
I would make an app in React (PWA) with a light back-end in Node.js just for parsing responses from an ASP.NET Core Web API.
Maybe, .NET Core will end the reign of Java in the "back-end world", but JavaScript is part of the web standard.
Thanks a lot Manuel for participating in this discussion :)
I really appreciate your comment and recommendations :)
But, what do you think of building a completed API with GraphQL using NodeJS , would it be better than using ,NET core, instead ?
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 :)
Could you please share with us a link about how to build Node.js for parsing responses from ASP.Net core web api and what is the benefit from using this technique :) .