MVC
Is MVC a pattern or framework ?
"MVC" is an "architectural pattern" which in turn can make use of several "design patterns", if needed.
A framework is an actual implementation of some sort, designed to be extended, adapted or customised as appropriate to the needs of your application.
what's the difference between design pattern and architectural pattern ?
- a Design Pattern is a solution to a rather localized problem - like "how can several classes share and customize a basic algorithm" -> Template Method.
- an Architectural Pattern is a solution to a rather global problem and therefore often more abstract than a Design Pattern - like "how can I shape the system, so that changes in the UI don't affect the model" -> MVC.
In J2EE, there are a lot of design patterns, like Session Facade, Value Object, etc...
Are these Architectural Patterns ?
No, those are Design Patterns - they are rather affecting a small number of objects instead of the whole architecture, afaik.
"MVC design pattern, MVC framework, MVC architecture"
Design Pattern - is a solution to a recurring software problem. It's a reusable solution. Tried and tested.
Architecture - is more abstract and is a way of looking at design. Every design has an architecture.
Framework - is an implementation of an architecture which consists of classes and interfaces that control the flow of execution of application that are based on a particular framework.
Example: Struts.
Down sides of MVC pattern.
Link - I
Link - II
"MVC" is an "architectural pattern" which in turn can make use of several "design patterns", if needed.
A framework is an actual implementation of some sort, designed to be extended, adapted or customised as appropriate to the needs of your application.
what's the difference between design pattern and architectural pattern ?
- a Design Pattern is a solution to a rather localized problem - like "how can several classes share and customize a basic algorithm" -> Template Method.
- an Architectural Pattern is a solution to a rather global problem and therefore often more abstract than a Design Pattern - like "how can I shape the system, so that changes in the UI don't affect the model" -> MVC.
In J2EE, there are a lot of design patterns, like Session Facade, Value Object, etc...
Are these Architectural Patterns ?
No, those are Design Patterns - they are rather affecting a small number of objects instead of the whole architecture, afaik.
"MVC design pattern, MVC framework, MVC architecture"
Design Pattern - is a solution to a recurring software problem. It's a reusable solution. Tried and tested.
Architecture - is more abstract and is a way of looking at design. Every design has an architecture.
Framework - is an implementation of an architecture which consists of classes and interfaces that control the flow of execution of application that are based on a particular framework.
Example: Struts.
Down sides of MVC pattern.
Link - I
Link - II
posted by Vishnu at 5:11 AM
0 Comments:
Post a Comment
<< Home