ASP.NET MVC performance?

Question

Although I am still new to ASP.NET MVC, my manager asked me to get an ASP.NET MVC performance report. In fact, we plan to develop real life, some kind of large system using ASP.NET MVC. Questions:
1- Is this a goona scale for a fairly large system?

2. Is it going to be easy for developers in a short “week” time?
3- Are there any real life systems that are created using ASP.NET MVC? "Except NerdDinner"
4- How can MVC save some ASP.NET development time?

Answer 1

If in performance your manager really means "how long does it take to write function X?" then, quite possibly, you will not be so productive in the short term with ASP.NET MVC. However, a much better separation of problems within the framework compared to web forms means that it is much easier to test and write well-structured code for.

This will give you improved long-term performance, but probably due to short-term performance. If you can make your manager see the past, then you are winning. Good luck with that!

To answer your direct questions:

• Will it scale?
  • It is definitely built on the high-performance ASP.NET platform and doesn’t bring a lot of Webforms with it.
• Is it not easy for developers to take "weeks" in a short time?
  • Depending on the current qualifications of your developers. If they are familiar with web development and the MVC pattern, this should easily come to them. If they are only familiar with ASP.NET Webforms drag-and-drop-with-some-code-behind, then they will have a whole new paradigm to find out what takes time.
• Are there any real life systems created using ASP.NET MVC?
  • This site is a great example.
• How can MVC save some ASP.NET development time?
  • In my original answer. However, it can also save time in the long run, as you don't rely heavily on structure, so don't put yourself in the corner of workarounds that can often occur in Webforms.

Answer 2

Reply # 3 - yes, you are using it right now: o) What was overflowing with the stack?

Answer 3

• Yes, it will scale well for large systems, certainly better than Forms.
• Depends, developers are already well indexed in ASP.NET. Forms can make transitions difficult. In some aspects, classic ASPers may seem oddly familiar. If developers are well informed about how HTTP works and the benefits of the general MVC approach, this should not be a big problem.
• You use one
• Using unit tests is the key to getting the most out of MVC, this will save you a ton of time while debugging.

Answer 4

The most interesting question, in my opinion, No. 4 is how can ASP.NET MVC be used to save development time?

He can, having created the infrastructure of the application on which all your functions and functionalities will be created.

Ayende has a really interesting post about this.

I think that many ASP.NET MVC developers will agree with me that ASP.NET MVC is by no means ready to create functions of complex applications - you should make some efforts to fit the framework to your application, and only after that you You can actually begin to get an advantage from its use.

Answer 5

It definitely scales. But performance versus web forms? If you are not very good at web forms, there is no problem that web forms are faster on the fly under RAD conditions.

Yes, a good TDD for ASP.NET MVC, but you need to understand that you are testing a lot of materials that are embedded in web forms, such as gridview, and all these beautiful custom drag and drop controls. You save a lot of time not to test these inline controls when you create web forms, while in MVC you run your own, and yes, you better write more code to test them. Thus, the testability gain is actually an illusion.

I will not jump into MVC until I see something similar to the gridview RAD type.

It also helps if you know CodeSmith and you can automate all the tedious repetitive code in MVC. TDD once, then create a CodeSmith template, then you just generate your code.

Answer 6

This is my point.

Will it scale? The truth is, no one has sent a decent test benchmark with equivalent architectures for comparison. Just words without tests.

Is it easy for developers to take "weeks" in a short time? Probably the base material is yes, but the hard material is not.

Are there any real life systems created using ASP.NET MVC? As said yes.

How can MVC reduce ASP.NET development time? People said that because there is a “much better separation of problems” in the code, magic is slowly happening and there is a surge in performance. I have been programming with Turbo Pascal for a long time. My “look” with MVC reminds me of the old days with DOS and Pascal. No good visual links to one screen during development. Instead of a single web form with some controls inside the visual studio, you have an object explorer full of files. At this time, I could not understand how this model could be more productive, simply suggesting a "better separation of problems."