Skip to content

What is the difference between Design Pattern Vs Architecture Pattern Vs Architecture Style?

These three things (Design Pattern Vs Architecture Pattern Vs Architecture Style) usually confuse most software developers or solution architects. Although they look similar there are huge differences between them, so it is essential to be able to distinguish.

In this post, I will use the theory of KISS (keep it simple stupid) to explain these.

Design Pattern:- Design patterns are normally working on a code level, for example, if someone says this is a Factory design pattern then this person must be able to explain the Factory pattern by demonstrating the flow in their pseudo-code or code. The logic must be clearly presented at the code level.
More examples of Design Patterns are Factory Design Pattern, Iterator Design Pattern, Singleton Design Pattern.

Architecture Pattern: If you say Architecture pattern then it is the block level diagram for example MVC (Model, View, and Controller) is an Architecture pattern. We can say Controller has the majority of the role in communicating between a view and a model. Some more examples of Architecture Patterns are: MVC (Model View Controller), MVP (Minimum Viable Product), MVVM (Model-view-ViewModel)

Architecture Style: Architecture Style is just the principles on which we are basing our development process. For example, REST is an architecture style that follows HTTP protocol. Some more examples of Architecture style are REST (Representational State Transfer), SOA (Service Oriented Architecture), IOC (Inversion of Control).

Leave a Reply

Your email address will not be published. Required fields are marked *