Design-Pattern

The Command Design Pattern encapsulates a request as an object, thereby letting you parameterize other objects with different requests.

The Prototype Pattern specifies the kind of objects to create using a prototypical instance and create new objects by copying this prototype

The State Design Pattern allows an object to alter its behavior when its internal state changes. The object will appear to change its class.

The Bridge Design Pattern decouples an abstraction from its implementation so that the two can vary independently. This pattern is also known as Handle/Body.

The Composite Design Pattern composes objects into tree structures to represent part-whole hierarchies and lets clients treat individual objects and compositions of objects uniformly.

Mediator Design Pattern defines an object that encapsulates how a set of objects interact and keeps the objects from referring to each other explicitly.

The Memento Design Pattern allows to capture and externalize an object’s internal state so that the object can be restored later without violating encapsulation

Introduction In the last post, I wrote about the Gang of Four (GoF) Builder Design Pattern. In this post, we will look at the builder pattern from the Effective Java…

The builder design pattern separates the construction of an object from its representation so that the same process can create different representations.

The chain of responsibility design pattern chains the receiving objects and pass the request along the chain until an object handles it.