Why is the MVC paradigm best for web applications?

Question

I'm sure my professor will ask me why I decided to use MVC for my web application.

In truth, I'm new to MVC. I read about it, I create a blog application using it, I think it is very logical to approach the problem this way.

But why? O_O I draw a space. What’s best suited than saying building an N-tier app?

Answer 1

Well, basically: separation of problems at the level of use, and not at the physical level.

Quote PoEAA on MVC

MVC breaks down user interface interaction into three different roles.

With MVC, you separate presentation (V, C) from domain logic (M), and also separate user interface (C) behavior from user interface (V) display. This is much more convenient than mixing all three problems into one, and also promotes reuse and testing. This allows you to better solve complexity.

This does not apply only to web applications. It is suitable for any application with domain logic and user interface. With that said, I would not say that MVC is the most suitable template for a web application. If all you want to do is put in, say, a contact form on the Internet, then just an on-page script is enough. If you only have a bunch of static pages, MVC is also redundant. Since with any templates, it depends on the problem you want to solve.

As for the n-level, the "classic" MVC did not provide for its use on the Internet. When presenting the user interface occurring in the browser and controller on a remote server, MVC on the Internet is always also a multi-level architecture, therefore, the difference between usecase and physical at the beginning. MVC is simply not interested in where this happens.

See also:

• What is MVC and what are its benefits?
• MVC VS N-Tiers