5

Every literature that is searched said that "MVC - is a design pattern assigns..." and the same such pattern as Singleton describes as "a software design pattern".

But WHY? These are different things that specify concepts on different levels of developing. In one MVC project you can have few Singleton, Factory and Unit of Work for example. But MVC and all these patterns still will be called 'design patterns'.

namae
  • 17
  • 4
Roman Makarenko
  • 73
  • 2
  • 7
  • MVC is a design pattern because 1) it fits the definition of a design pattern, and 2) because it is recognized as a design pattern. I don't really understand the basis for your questioning it. – Stephen C Nov 26 '17 at 07:13
  • There are multiple design patterns in several classifications then can be used together as needed. So I do not get the question. See https://en.wikipedia.org/wiki/Software_design_pattern#Classification_and_list. Lets try to ask it the other way around: why can't MVC and singleton not be both design patterns. What would be your answer? – Peter Bons Nov 26 '17 at 07:17
  • Same question: https://stackoverflow.com/questions/4192887 – Yousha Aleayoub Jun 11 '20 at 09:44

1 Answers1

15

You were confused here with architectural and design pattern. In this case, both are different.

MVC is an architectural pattern where as Single-ton is an design pattern.

Design patterns - are for solving some common technical problems which are addressed using OOPs concepts. Example: How to write a code to have a single object for a single user rather than creating many such objects which results in lack of memory.

Architectural Patters - are for solving software application architecture problems which mostly addresses scalability, reliability, security, etc.,. Example: How easily we can handle an application if its size gets increased ?

Sudarson Soundararajan
  • 237
  • 2
  • 6