MVC and Design patterns

Question

User1983249378 posted

I got to know that there is a difference between Software Architecture and Software Design pattern. An Architecture can have and design pattern in it.

My question is we are going to build and enterprise level application and doing it on MVC3. So is it necessary to implement Design pattern in it or my perception is MVC itself an architectural design pattern .

Correct me Thank you.

Answer 1

User351203563 posted

Practically design patterns provide approaches to solve/address certain problems or conditions that we come across during developing a software application. It’s not related to the size of the application. For example, to have better isolation and loose coupling we use MVC. To have single instance of class in a scope we use Singleton. To provide better integration of data layer we use repository pattern or a provider pattern. It’s not necessary that you always need to use a pattern. So you can actually see if you need a pattern to address a particular integration or implementation.  As patterns are proven way of achieving certain requirements, using them help us avoid complexity. But again its one own decision to choose. As you mentioned correctly, Asp.Net MVC itself is using the MVC design pattern. But it’s not the end, for a complete enterprise solution you may need multiple patterns to address different issues or integrations as mentioned above.

Answer 2

User-37275327 posted

my perception is MVC itself an architectural design pattern

Yes, you are correct.

we are going to build and enterprise level application and doing it on MVC3

This depends on your requirement. My personnel feeling is, if it is a ecommerce app or a web site expose to internet, better do using MVC. Because you have total control over the url. if it is intranet app, better to use webforms. There are many thirdparty controls  available on the market. Again your choice at last.