What is an MVC framework and why is it necessary/u

Question

I know that an MVC framework allows you to separate business logic, data base access and presentation, but why do we need a framework to do this.

Can't we just keep our classes separated, perhaps using different packages/folders for the model, view and controller classes?

Answer 1

An MVC framework is a framework written to split up the the business logic, database access and presentation.

This is very useful in most web applications, and now lately into software/desktop applications.

This is due to the fact that following the MVC model, your code will be much clearer, cleaner and you keep your application DRY (Do not Repeat Yourself).

You can write your own classes and separate them into Model, View and Control. But again, you will need a framework to help you in accomplishing certain tasks. Like a List control in ASP.NET, or PHP framework being able to help you translate text between languages and so on. (Oh why reinvent the wheel?!)

Answer 2

MVC and framework is a different thing. MVC is just an architectural pattern, which can be applied with any project, with or without framework.

So you don't need a framework to do this. You can separate them by yourself. :)

Answer 3

Perhaps this is just a linguistic thing. I've seen "frameworks" referring to themselves as a DSL -- Domain Specific Language.

And you don't need a framework But here's something to consider: You already know for a web app you're going to want to do a few common things... route URLs, render pages, etc. Why re-write it all? For other problem domains you'll have generic things to do as well.