This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
This question has cropped up here a few times. I believe the consensus is that what most people know as "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.
I would agree with Frank that MVC is rather an Architectural Pattern than a Design Pattern - but the distinction probably isn't that important. Struts is *one* implementation of the pattern - there are, of course, an uncountable amount of others.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Hi all, whatz the difference between design patterns and architectural pattern
Joined: Jul 11, 2001
Originally posted by Pradeep Bhat: Hi all, whatz the difference between design patterns and architectural pattern
It's mostly a matter of magnitude: - 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