DEV Community

.NET Conf 2022 in a Nutshell🥜 (Key Highlights to Know)

ByteHide on November 16, 2022

If you’re like me and didn’t have the time to follow the .NET Conf 2022 , fear not! Microsoft has teamed up with various venues across the country...

Read full post

Raí B. Toffoletto • Nov 17 '22

Nice summary ! Tnx. Looking forward to work with those improvements.

But just a note... put a pile of salt in any benchmark made by companies. As I see at work, .NET and Node don't have this disparity in numbers.

ByteHide • Nov 17 '22

Thanks for your time Raí, glad you liked it!

I agree with you regarding the benchmarks, on one hand I understand the companies that want to show (with numbers) what they can do and, on the other hand, I understand the final customers/consumers, that when they test it themselves, maybe they will be upset because of the difference they get with respect to the benchmark shown by the company.

You have commented that in your work Node and .NET do not have that disparity, could you explain what is the scenario/use? The truth is that now you have left me with the curiosity hahaha

cheers :)

Raí B. Toffoletto • Nov 18 '22

We haven't heavily benchmarked both, but all our projects are basically web apis or websites/webbapps made with nextjs (node as server) or razor pages. Usually they are deployed on 1 shared cpu with one 1gb max of ram... they both handle well lots of concurrent requests and data processing, so I can't see a practical disparity on performance. However both tecnologies scale up very differently, so to handle that amount showed in the charts strategies are different. (Throw more cores and ram do nothing to node if you don't spawn multiple instances and use a load balancer for example) So I wonder how they got the numbers. That's all! 🙂

disclaimer: And although personally I'm very critical to Microsoft practices most of the time I do like a lot dotNet to build web apis!! I had to port projects using dotnet core 2.2 to 6. and I think it didn't take me even a full hour.