Design Patterns
By definition, Design Patterns are reusable solutions to commonly occuring problems(in the context of software design). Design patterns were started as best practices that were applied again and again to similar problems encountered in different contexts. They become popular after they were collected, in a formalized form, in the Gang Of Four book in 1994. Originally published with c++ and smaltalk code samples, design patterns are very popular in Java and C# can be applied in all object oriented languanges. In functional languages like Scala, certain patterns are not necesary anymore.
Creational Design Patterns
- Ensures that only one instance of a class is created and Provides a global access point to the object.
When to Use: Singleton pattern should be used when we must ensure that only one instance of a class is created and when the instance must be available through all the code. A special care should be taken in multi-threading environments when multiple threads must access the same resources through the same singleton object.
Common Usage: There are many common situations when singleton pattern is used:
- Logger Classes
- Configuration Classes
- Accesing resources in shared mode
- Other design patterns implemented as Singletons: Factories and Abstract Factories, Builder, Prototype
- Creates objects without exposing the instantiation logic to the client and Refers to the newly created object through a common interface.
When to Use: Factory pattern should be used when: - a framework delegate the creation of objects derived from a common superclass to the factory - we need flexibility in adding new types of objects that must be created by the class.
Common Usage: Along with singleton pattern the factory is one of the most used patterns. Almost any application has some factories. Here are a some examples in java:
- factories providing an xml parser: javax.xml.parsers.DocumentBuilderFactory or javax.xml.parsers.SAXParserFactory
- java.net.URLConnection - allows users to decide which protocol to use
- Defines an interface for creating objects, but let subclasses to decide which class to instantiate and Refers to the newly created object through a common interface.
When to Use: Factory Method pattern should be used when:
- a framework delegate the creation of objects derived from a common superclass to the factory
- the base factory class does not know what concrete classes will be required to create - delegates to its subclasses the creation of concrete objects.
- factory subclasses subclasses are aware of the concrete classes that must be instantiated.
Factory method pattern, compared to Factory pattern replace the factory with an abstract class and a set of concrete factories subclasses. The subclasses are responsible for creating concrete product objects; for factory method is possible adding new product classes without changing the abstract factory. The same result can be achieved for simplified factory pattern if reflection is used.
Common Usage: Along with singleton pattern the factories are the most used patterns. Almost any application has some factories. Here are a some examples:
- factories providing an xml parser: javax.xml.parsers.DocumentBuilderFactory or javax.xml.parsers.SAXParserFactory
- Offers the interface for creating a family of related objects, without explicitly specifying their classes.
When to Use: Abstract Factory should be used when:
- A system should be configured with one of multiple families of products
- A system should be independent of how its products are created, composed and represented
- Products from the same family should be used all together, products from different families ahould not be used togheter and this constraint must be ensured.
- Only the product interfaces are revealed, the implementations remains hidden to the clients.
Common Usage: Examples of abstract factories::
- java.awt.Toolkit - the abstract superclass of all actual implementations of the Abstract Window Toolkit. Subclasses of Toolkit are used to bind the various components to particular native toolkit implementations(Java AWT).
- javax.swing.LookAndFeel - an abstract swing factory to swithct between several look and feel for the components displayed(Java Swing).
- java.sql.Connection - an abstract factory which create Statements, PreparedStatements, CallableStatements,... for each database flavor.
- Defines an instance for creating an object but letting subclasses decide which class to instantiate and Allows a finer control over the construction process.
When to Use: Abstract Factory should be used when:
- A system should be configured with one of multiple families of products
- A system should be independent of how its products are created, composed and represented
- Products from the same family should be used all together, products from different families ahould not be used togheter and this constraint must be ensured.
- Only the product interfaces are revealed, the implementations remains hidden to the clients.
Common Usage: Examples of abstract factories::
- java.awt.Toolkit - the abstract superclass of all actual implementations of the Abstract Window Toolkit. Subclasses of Toolkit are used to bind the various components to particular native toolkit implementations(Java AWT).
- javax.swing.LookAndFeel - an abstract swing factory to swithct between several look and feel for the components displayed(Java Swing).
- java.sql.Connection - an abstract factory which create Statements, PreparedStatements, CallableStatements,... for each database flavor.
- reuses and shares objects that are expensive to create.
When to Use: Basically, we'll use an object pool whenever there are several clients who needs the same stateless resource which is expensive to create.
Common Usage: The most common situations when object pool pattern is used:
- Database Connections
- Remote Objects
Behavioral Design Patterns
- It avoids attaching the sender of a request to its receiver, giving this way other objects the possibility of handling the request too.
The objects become parts of a chain and the request is sent from one object to another across the chain until one of the objects will handle it.
- Encapsulate a request in an object, Allows the parameterization of clients with different requests and Allows saving the requests in a queue.
- Given a language, define a representation for its grammar along with an interpreter that uses the representation to interpret sentences in the language / Map a domain to a language, the language to a grammar, and the grammar to a hierarchical object-oriented design.
- Provide a way to access the elements of an aggregate object sequentially without exposing its underlying representation.
- Define an object that encapsulates how a set of objects interact. Mediator promotes loose coupling by keeping objects from referring to each other explicitly, and it lets you vary their interaction independently.
- Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically.
- Define a family of algorithms, encapsulate each one, and make them interchangeable. Strategy lets the algorithm vary independently from clients that use it.
- Define the skeleton of an algorithm in an operation, deferring some steps to subclasses / Template Method lets subclasses redefine certain steps of an algorithm without letting them to change the algorithm's structure.
- Represents an operation to be performed on the elements of an object structure / Visitor lets you define a new operation without changing the classes of the elements on which it operates.
- Provide an object as a surrogate for the lack of an object of a given type. / The Null Object Pattern provides intelligent do nothing behavior, hiding the details from its collaborators.
Structural Design Patterns
- Convert the interface of a class into another interface clients expect. / Adapter lets classes work together, that could not otherwise because of incompatible interfaces.
- decouples abstraction from implementation so that the two can vary independently
- Compose objects into tree structures to represent part-whole hierarchies. / Composite lets clients treat individual objects and compositions of objects uniformly.
- add additional responsibilities dynamically to an object.
- use sharing to support a large number of objects that have part of their internal state in common where the other part of state can vary.
- capture the internal state of an object without violating encapsulation and thus providing a mean for restoring the object into initial state when needed.
- provide a “Placeholder” for an object to control references to it.