• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

When not to use MVC ??

 
Femi Byte
Ranch Hand
Posts: 40
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The literature touts quite a lot of benefits of using the MVC pattern, which to me are really the benefits of designing by separation of concerns. I want to know whether there are any scenarios when it would be detrimental to use MVC or separation of concerns in designing a system or application.
 
sivan jai
Ranch Hand
Posts: 115
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Separation of concerns is truly the first step towards maintainibility, extensibility, scalability - so I dont see any place where you wont need separation.
 
Deepak Bala
Bartender
Posts: 6663
5
Firefox Browser Linux MyEclipse IDE
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
when it would be detrimental to use MVC or separation of concerns in designing a system or application.


When a view model and controller are not used ? MVC applies to various frameworks like Struts, Swing etc. It would not make sense for example to use MVC for a javaMail API (Assuming the APIs responsibility to ONLY to send emails)
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic