Design Pattern is essentially an architectural term that was introduced in the software engineering context by Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides, The Gang of Four GoF, in their book Design Patterns: Elements of Reusable Object-Oriented Software by GoF in 1994 (1).

Design patterns are a collection of reusable solutions and best practices to common problems in software design. It’s not an algorithm that you can use directly into your code, rather it’s a template, UML diagrams and descriptions of how you should go about solving this problem, how should you design the classes and link them together. Those patterns are proven, tested paradigm that maintains the code modular, clean and easily maintained.

Many says that you need to perfect your understanding of OOP before you could actually understand Design Patterns. And For me, personally, I found it so much easier to understand Object-Oriented concepts and terms after my instructor on one of my classes introduced Design Patterns to us. Many of the OOP concepts (abstract classes, polymorphism, interfaces), while I understood how they work and memorized some of their uses, became so much clearer when I started learning design patterns and started to appreciate the beauty of OO.

The gang of four broke down their design patterns into a 3 categories. I think now they’re 4 categories. Nevertheless, Below is a list of patterns that the GoF introduced sorted out by their type.

In this blog, I’ll share with you some examples and cases where Design patterns really came to my aid when I worked on different problems.

Observer Design Pattern is coming up soon…

The following is copied From Design Patterns - Wikipedia so I can link them to my blog posts in the future

Patterns by Type


Creational patterns are ones that create objects for you, rather than having you instantiate objects directly. This gives your program more flexibility in deciding which objects need to be created for a given case.

  • Abstract factory pattern groups object factories that have a common theme.
  • Builder pattern constructs complex objects by separating construction and representation.
  • Factory method pattern creates objects without specifying the exact class to create.
  • Prototype pattern creates objects by cloning an existing object.
  • Singleton pattern restricts object creation for a class to only one instance.


These concern class and object composition. They use inheritance to compose interfaces and define ways to compose objects to obtain new functionality.

  • Adapter allows classes with incompatible interfaces to work together by wrapping its own interface around that of an already existing class.
  • Bridge decouples an abstraction from its implementation so that the two can vary independently.
  • Composite composes zero-or-more similar objects so that they can be manipulated as one object.
  • Decorator dynamically adds/overrides behavior in an existing method of an object.
  • Facade provides a simplified interface to a large body of code.
  • Flyweight reduces the cost of creating and manipulating a large number of similar objects.
  • Proxy provides a placeholder for another object to control access, reduce cost, and reduce complexity.


Most of these design patterns are specifically concerned with communication between objects.

  • Chain of responsibility delegates commands to a chain of processing objects.
  • Command creates objects which encapsulate actions and parameters.
  • Interpreter implements a specialized language.
  • Iterator accesses the elements of an object sequentially without exposing its underlying representation.
  • Mediator allows loose coupling between classes by being the only class that has detailed knowledge of their methods.
  • Memento provides the ability to restore an object to its previous state (undo).
  • Observer is a publish/subscribe pattern which allows a number of observer objects to see an event.
  • State allows an object to alter its behavior when its internal state changes.
  • Strategy allows one of a family of algorithms to be selected on-the-fly at runtime.
  • Template method defines the skeleton of an algorithm as an abstract class, allowing its subclasses to provide concrete behavior.
  • Visitor separates an algorithm from an object structure by moving the hierarchy of methods into one object.


Software design pattern - Wikipedia


(1) You see how me coming to the world enlightened and inspired all the brilliant minds around the world