Have Geek Brain

Advantages and Disadvantages of Using the MVC Design Pattern (Model View Controller)

I'm at a point in my design where I am contemplating deleting an MVC project for performance reasons, but not sure if straight forward PHP pages with header / footer components will do my MVC setup (using PHP / Zend). I feel like it will be.

Comments?

+1


a source to share


4 answers


What is the value of your time? From your performance? About your code health?

against.



What is the cost of an additional server?

+3


a source


It depends on what you are building. MVC can certainly be overkill for some things and not even applicable to others. Weigh this against future maintenance, working with other developers, how much of the MVC design pattern are you going to rewrite yourself, etc.



0


a source


This article discusses MVC and its inventive DCI paradigm that could be a contender for traditional OO.

0


a source


I am familiar with MVC from its original Smalltalk-80 context. The decision on whether to use MVC or something else is about code clarity, not performance. If there are specific performance issues with MVC in PHP, I am not aware of them.

But again, the main reason for moving to MVC is that separation of concerns is an important factor in ensuring that software maintains and maintains over time.

0


a source






More articles:


All Articles