MVC
MVC is one of many design patterns used for the development of software. MVC stands for Model-View-Controller. Database information is held in the Model. The processes that controls how the data is displayed is in the view. The controller files handle requests from the user, and provides the means for the model data to get to the View. Ruby on Rails is MVC.
Why MVC
The MVC design pattern is well established and has been around for a number of years. The structured approach encourages good coding practices. It allows unit testing and agile development. It can simplify database access using the entity framework. It is relatively easy to make large scale changes to an MVC web project.
Is MVC for you
MVC may not be the right solution for you. The following may help in making a decision.
No to MVC
- A small website of a few pages may not suit MVC. This is because there are a number of files a folders required even for one web page.
- Your existing website does not require modification or future modifications are easily made
- Your design team is expert in the web technology currently being used.
- Your database structure is stable and unlikely to change.
- Your new web project requirements are not suitable for implementation using MVC
Yes to MVC
- You are started a new web project requiring a database.
- You are starting a complicated web project.
- Your existing website is becoming unmanagable.
- Your database structure likely to change.
- Your new web project requirements are suitable for implementation using MVC
- You are able to run IIS7
ASP.NET MVC enables you to build Model View Controller (MVC) applications by using the ASP.NET framework. ASP.NET MVC is an alternative, not a replacement, for ASP.NET Web Forms that offers the following benefits:
- Clear separation of concerns
- Testability - support for Test-Driven Development
- Fine-grained control over HTML and JavaScript
- Intuitive URLs