Why do we need mvc pattern

Ask Question. Asked 10 years, 2 months ago. Active 6 years, 6 months ago. Viewed k times. Improve this question. MVC is simply a implementation of Seperation of Concerns.

Any implementation will do. Not using Seperations of Concerns tends to lead towards a Big ball of mud — Raynos. Raynos: Perhaps. But that's not where the "hype" is going. Don't let it influence you too much. I can't think of a solid alternative.

But Separation of Concerns is a property of OO development. Add a comment. Active Oldest Votes. Martin Fowler agrees with your confusion about MVC: I don't find it terribly useful to think of MVC as a pattern because it contains quite a few different ideas.

Improve this answer. Gnawme Gnawme 1, 8 8 silver badges 7 7 bronze badges. I feel this depends much upon the problem you are tackling. I see the separation as follows: Model - how do we represent the data? View - how do I render the result? Unk Unk 1 1 silver badge 3 3 bronze badges. The database? Because everyone I've talked to says that such actions still belong in a model, not in controllers. What counts as HTTP stuff?

I would include the following in a controller: Unmarshalling HTTP request parameters, checking the parameters for basic sanity, determining what needs to be done, visiting appropriate model objects to read, write or both , producing a final result based upon the model's responses, passing that off to the view.

A silly example of something only a controller would be used for might be a web service generating a random number - in this case there is no 'model' to look at in my mind at least Those are all model concerns. Even "deciding what needs to be done" the "front controller" is a model. Not to mention controllers are useful for not hard-coupling your models to your views.

As well as allowing you to connect many views to many models through one controller. Billy: if you allow a view to "mess" with the model - other than quering it for its values - you end up with views that are more like controllers. The controller mediates between the Model behaviour and data of the domain and GUI on-screen representation of the model. The view just passes interactions to the controller user clicked The controller decides what if any needs to be called on the model.

Show 6 more comments. You shouldn't. Side note: I don't develop web apps professionally, so there may be something that I'm missing. Demian Brecht Demian Brecht I totally agree, good answer. The controller isn't always necessary, it's just meant as a strategy for the view to communicate with the model.

Falcon: See, that's my confusion. The scope of this is bright and demanding. Almost all the top companies and industries based on websites use MVC design patterns for developing User Interfaces and models. This is used in programming platforms, and the right audience for learning these designs are the developers and programmers. The learners should be passionate about learning the design patterns and using and applying them accordingly to their projects.

It has so much in store for its developers. The users learn many skills and methods by using the MVC theory. There are many skills associated with these design patterns, and learning this technology will help the learner boost not only their skills but also their future prospectus. These skills will help the learners in the long run and provide influential growth in their careers.

Understanding it is an important technique. This technology allows creating reusable and separate models that can be easily upgraded. Time taken to develop applications become less, and the developers create an efficient application. The MVC theory is a basic concept of computer programming and helps in giving several web development services and projects. You can also go through our other suggested articles to learn more —.

Submit Next Question. By signing up, you agree to our Terms of Use and Privacy Policy. Forgot Password? This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the cookie policy. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to our Privacy Policy.

Popular Course in this category. Course Price View Course. Free Software Development Course. And even more so when I started applying these concepts to an actual application. By taking a step back to focus on what MVC is and what it can accomplish, it's much easier to understand and apply the pattern to any web application.

Today the MVC pattern is used for modern web applications because it allows the application to be scalable, maintainable, and easy to expand.

The MVC pattern helps you break up the frontend and backend code into separate components. This way, it's much easier to manage and make changes to either side without them interfering with each other. But this is easier said than done, especially when several developers need to update, modify, or debug a full-blown application simultaneously. To better illustrate the MVC pattern, I've included a web application that shows how these concepts all work.

The model's job is to simply manage the data. In the Car Clicker application, the model object contains an array of car objects with all the information data needed for the app. It also manages the current car being displayed with a variable that's initially set to null. Both views have two critical functions that define what each view wants to initialize and render. The controller's responsibility is to pull, modify, and provide data to the user.