Good question, but hard to answer. I think Node.js with JavaScript/TypeScript is easier to start as a beginner. Also I think Node.js is more widely used in companies. I don't think you'll go wrong with either of them :)
For reading queries, if you use other ORM like Dapper, you will gain at least 2x performance difference versus EF Core. If you want to push the limits, you will go with a full raw SQL query. In my personal opinion. You should not benchmark ORM's with raw SQL queries because of its performance differences. Don't compare beans with apples and vice versa.
Thank you for sharing your opinion :) I know, comparing EF core versus raw SQL is not optimal, but I figured it is good enough as the benchmarks concentrated on the performance differences of ASP.NET Core and Node.js.
Man, I just knew you were going to say the other one and I was going to come here and complain. This is exactly my finding too, I don't want to spoil in the comments, watch the clip yall.
Nodejs has never been about performance, it's always been if your app doesn't require that big of a performance like 90% of the apps are fine working in Node then go to Node to keep your frontend and backend in the same language (now you even have Bun and Deno) Otherwise grab at Java and C# to improve performance a bit or Zig and Rust to improve it a lot Finally I never understood Python, Ruby and PHP's role in the stack; they are all slower than JS and don't ever offer that frontend/backend same language dev experience
On my experience with django with traditonal html, css, js, and bootstrap, I rarely touch JS (except for manual ajax that not covered by python package). Maybe adding htmx on top of that can more minimalize JS writing for ajax.
PHP has a well established MVC ecosystem that comes with battery included or at least opinionated/highly structured with a decent cli integration that simplifies debugging or startup. But yeah, it basically takes a degree to master whereas Node is very straightforward
You do not necessarily measure api benchmark id you do heavy calculations. For API speed I'd rather be interested in data about request handling, routing or dynamic content creation. For heavy computation or generating data you could build any api to cpp rust or other languages that could lift that weight for you. Regardless, ASP would be faster anyway
Good test! But EF against raw SQL most of the time is not comparable. Maybe .NET Core could be even faster. Cheers!
Yeah, I did not care enough about database access for this test, will keep it in mind for future benchmarks. Thank you for your comment :)
Which one is good for 2025 as a fresher developer should i go for .net or go with Nodejs? To easily get a job as a fresher
Good question, but hard to answer. I think Node.js with JavaScript/TypeScript is easier to start as a beginner. Also I think Node.js is more widely used in companies. I don't think you'll go wrong with either of them :)
go with Go
Thanks for this informative comparison. What about the difference in bench mark between .net and python (gjango/fastapi)
Thank you for your comment :)
I already thought about comparing asp.net core with python, maybe I will make a video about this
Thank u
EF does some caching in the background so this means nothing.
Not between requests.
You pick EF Core versus raw SQL... That's not comparable.
For reading queries, if you use other ORM like Dapper, you will gain at least 2x performance difference versus EF Core. If you want to push the limits, you will go with a full raw SQL query. In my personal opinion. You should not benchmark ORM's with raw SQL queries because of its performance differences. Don't compare beans with apples and vice versa.
Thank you for sharing your opinion :)
I know, comparing EF core versus raw SQL is not optimal, but I figured it is good enough as the benchmarks concentrated on the performance differences of ASP.NET Core and Node.js.
Man, I just knew you were going to say the other one and I was going to come here and complain. This is exactly my finding too, I don't want to spoil in the comments, watch the clip yall.
Nodejs has never been about performance, it's always been if your app doesn't require that big of a performance like 90% of the apps are fine working in Node then go to Node to keep your frontend and backend in the same language (now you even have Bun and Deno)
Otherwise grab at Java and C# to improve performance a bit or Zig and Rust to improve it a lot
Finally I never understood Python, Ruby and PHP's role in the stack; they are all slower than JS and don't ever offer that frontend/backend same language dev experience
On my experience with django with traditonal html, css, js, and bootstrap, I rarely touch JS (except for manual ajax that not covered by python package).
Maybe adding htmx on top of that can more minimalize JS writing for ajax.
PHP has a well established MVC ecosystem that comes with battery included or at least opinionated/highly structured with a decent cli integration that simplifies debugging or startup. But yeah, it basically takes a degree to master whereas Node is very straightforward
You do not necessarily measure api benchmark id you do heavy calculations. For API speed I'd rather be interested in data about request handling, routing or dynamic content creation. For heavy computation or generating data you could build any api to cpp rust or other languages that could lift that weight for you. Regardless, ASP would be faster anyway
Hmmmm....
.net core not usable for small projects