ASP.NET

We switched from django monolyth to .net microservices with ms sql accounting operations. May not be apple to apples comparison but we found ourselves in better place after the switch

We selected ASP.Net because of the market position. It is well known in combination with visual studio and IIS. Also, new colleagues know this and can be involved very quickly. No need to make a lot of investment in education. We do need to teach them the guidelines of our company.

As a previous developer in Java and PHP, I’ve found Asp.net to be much more user-friendly and better structured than the competition. Code completion, library availability, stack runtime, debugging, and general workflow are definitely a level up in my experience. Visual Studio provides a good integration of the technology and provides a pretty decent user experience.

We choose ASP.NET because our core business is working with the SAP HANA database using SAP Business One. We can develop state-of-the-art applications with Razor and Visual Studio 2022 fast and with excellent application performance response. Working SAP Hana with JAVA could be more challenging because it has fewer developers communities, and it could be harder to find a solution for a question.

ASP.NET and Visual Studio are the best combo to develop web applications faster and securely. This accelerates the implementation time of projects and the improvement of web applications.

There is a big difference between the two technologies, ASP.Net is more organized, more secured, the tools you can use for developing ASP.Net is way stronger and better supported, ASP.Net itself is more secured than PHP.

NodeJS is a popular technology because, in my opinion, when it was introduced it made significant improvements on how easy it was to work with a familiar language (JS) on the server-side. But, now that it's no more a new technology and other competitors have caught up, I find little reason to use it. JS is terrible, even with Typescript. The benefits of a fast, strongly-typed language that receives constant updates like C# are just, too many. Not to mention that NodeJS, while fairly fast, makes it hard to scale with more things that need to be managed by the developer or devops.

It’s possible to do the same thing with Apache, Nodejs, and so on. ASP.NET is easier to learn than other programs on their own, making it more accessible. Deploying and maintaining the application is a lot easier once you’ve completed the installation process. With each passing year, ASP.NET has been improving and expanding its compatibility.

I have used things like Java Struts in my time and I have found technologies from that era are often quite alike. They were a big step forward at the time - but I think there are better things to use now. ASP.NET and Struts were in that same era, they still work really well and do everything you need them to, but there are downsides. I just think we should move towards simpler code rather than all this unnecessarily complicated strongly typed code. As an example, how many classes make up the ASP.NET foundation code? Too many in my view. I would much rather use Express in NodeJS.

I don't like javascript that much, personally. Having a backend built on top of javascript in the case of Node.js leaves me lying awake at night. I prefer strongly typed languages and knowing I have the support of Microsoft behind my choice of systems. Node.js when I experimented was awkward to setup and not as intuitive as ASP.NET.

[ASP.NET] is built over a very solid framework, that for sure developers can depend on, and through the years it evolved very well to serve the market and developers need, with the different versions and design patterns it has you will always be able to do all the stuff needed with minimum efforts. Node.js is new technology and there isn't much support and documentation available for it out there.

ASP.NET has continuously delivered improvements and expanded compatibility over the past years. It integrates nicely with our existing applications and frameworks without being too invasive.

Other products could be used to do the same what ASP.NET achieves. For server code Nodejs could be used and for front-end Reactjs, Angular etc. could be used. What ASP.NET achieves is that you can do this combined thing in one framework. So learning is easy as compared to learning other separate technologies. Also after deployment managing of application also becomes quite easier.

ASP.NET makes it a lot easier to integrate with other systems, especially Microsoft services. It is much easier to make backend API's without too much code. There is good support from Microsoft and there is a huge community of developers. And as Zend Framework most is now open source too which is a plus.

We had MSDN subscriptions, and developers had this extensive skillset. Faster and easier than any other tools. The client also had apps running on an IIS server.

I will not select again and will not advise to use our clients

Familiarity, convenience, some of the core activities are built-in, good documentation.

ASP.NET is much easier to work with and ramp up than any other product that we tried. ASP.NET was also significantly cheaper to start coding with. We also had the resources on hand so we did not need to hire contractors or consultants, which also allowed us to go faster and cheaper. We had a lot of issues with WebSphere.

ASP.Net is more feature rich compared to the Laravel PHP Framework, which is why we eventually chose it. Laravel does make for a quicker "first start" when building an application, but the long term investment we needed in features and functionality caused us to weigh in favor of ASP.NET in the end.

Perl and Ruby on Rails were also evaluated as possible options to solve our business needs. ASP.NET is, of course, more expensive, but provided a robust and somewhat easier integration of the specific tool-set required to provide excellent service to our customers. The framework technology reduces coding time, and the resulting applications built on this framework are more secure. Monitoring is built-in, and common tasks are easier to perform.

Compared to other Monolithic solutions like Java, ASP.NET can certainly hold its own. C# along with .NET functionality is a lot more robust In my opinion then Java Spring or Java Struts. The documentation and configuration is a lot better and a lot better maintained. However I would still choose NodeJS for most cases, as it is a lot more dynamic and fast to develop, maintain and deploy.

PHP and the many associated frameworks are probably the main similar products around - however, the diversity and open source nature of these things can mean you are building on a moving foundation - the stability offered by ASP.NET is a plus for me and my team. The lie of the land may have changed for PHP more recently but historically that was an issue for me.

Compared to plain HTML/CSS/JS, ASP.Net adds many productivity tools and frameworks that allow for more rapid and robust development.

The in-house framework of ASP.NET reduces a lot of boilerplate code and also easier to start. The development environment is amazingly faster.