In this article, we will find something out about mediator pattern and some application of its pattern.
Let’s get started.
Table of contents
- Given Problem
- Solution of Mediator Pattern
- When to use
- Benefits & Drawback
- Application & Examples
- Wrapping up
Assuming that we have two classes such as Class1 and Class2. When each class want to communicate together, it has a reference to the other classes. So, it will call other classes directly.
Then, we have some problems:
- It makes our objects to tightly couple each other.
- It makes impossible to change the interaction independently from (without having to change) the objects, and it stops the objects from being reusable and makes them hard to test.
When each object want to communicate with many other objects, it needs to hold the reference of all objects. It makes our code to become difficult to control, and it takes resource so much.
For example, with chat application in mobile phone, to communicate between users, each user needt to hold the connections between them, so it does not make sense because it makes reduces the usage time of mobile phone, and it makes mobile phone’s CPU work permanently.
Finally, we will have some question about these problems?
- How can tight coupling between a set of interacting objects be avoided?
- How can the interaction between a set of objects be changed independently?
Solution of Mediator Pattern
Our problems is that the tightly couples between objects. To get rid of them, we need to create a central object and its responsibility is to manage the communication between the objects.
So, Mediator pattern was born. Its intent is to define an object that encapsulates how a set of objects interacts, reducing their dependency on one another.
The implementation of Mediator pattern will do the following steps:
We need to know exactly what the concrete objects that communicates together. Then, we create a separate Mediator object that encapsulates how a set of objects interact.
Objects interact with a Mediator object instead of interacting with each other directly.
This makes objects loosely coupled because they only refer to to and know about their mediator, have no explicit knowledge about each other.
When to use
- When there are lots of entities interacting in a similar manner and those entities should be decoupled.
Benefits & Drawback
Centralizes interaction behavior.
Makes changing the interaction behavior easy.
- When the number of meditors will grow, then it will become hard to maintain them.
To refer this pattern’s code, we can read the source code of Mediator pattern on Github.
Application & Examples
The mediator pattern is used in Java libraries to implement
Timerclass can be used to schedule threads to run one time or repeatedly at regular intervals. The thread objects correspond to the ConcreteColleague class. The
Timerclass implements methods to manage the execution of background tasks.
Java Concurrency Executor
Java Message Service (JMS) uses Mediator pattern along with Observer pattern to allow applications to subscribe and publish data to other applications.
- The key idea in this pattern is to let objects interact with each other indirectly through a common Mediator object that controls and coordinates the interaction.
Thanks for your reading.