Architecture vs Design Pattern

Link tham khảo: https://stackoverflow.com/a/4243407

Giống nhau: chúng đều là pattern. Mục đích là giải quyết 1 cấu trúc phức tạp thành những phần nhỏ đơn giản hơn

Khác nhau: ở một mức cao, chúng ta sử dụng architect pattern để giải quyết. Ở một mức độ thấp hơn, chúng ta sử dụng design pattern. Mức độ cơ bản nhất (implememtation level), chúng ta sử dụng programming paradigms

Patterns are distilled commonality that you find in programs. It allows us to deconstruct a large complex structure and build using simple parts. It provides a general solution for a class of problems.

A large complex software goes through a series of deconstruction at different levels. At large level, architectural patterns are the tools. At smaller level, design patterns are the tools and at implementation level, programming paradigms are the tools.

For a most simplistic view:

• Programming paradigms - specific to programming language

• Design patterns - solves reoccurring problems in software construction

• Architectural patterns - fundamental structural organization for software systems

Design patterns are usually associated with code level commonalities. It provides various schemes for refining and building smaller subsystems. It is usually influenced by programming language

While architectural patterns are seen as commonality at higher level than design patterns. Architectural patterns are high-level strategies that concerns large-scale components, the global properties and mechanisms of a system

If you have followed the thoughts laid above. You will see that Singleton is a "design pattern" while MVC is one of the "architectural" pattern to deal with separation of concerns.