Summer SALE

Mediator in TypeScript

Mediator is a behavioral design pattern that reduces coupling between components of a program by making them communicate indirectly, through a special mediator object.

The Mediator makes it easy to modify, extend and reuse individual components because they’re no longer dependent on the dozens of other classes.



Usage examples: The most popular usage of the Mediator pattern in TypeScript code is facilitating communications between GUI components of an app. The synonym of the Mediator is the Controller part of MVC pattern.

Conceptual Example

This example illustrates the structure of the Mediator design pattern and focuses on the following questions:

  • What classes does it consist of?
  • What roles do these classes play?
  • In what way the elements of the pattern are related?

index.ts: Conceptual example

 * The Mediator interface declares a method used by components to notify the
 * mediator about various events. The Mediator may react to these events and
 * pass the execution to other components.
interface Mediator {
    notify(sender: object, event: string): void;

 * Concrete Mediators implement cooperative behavior by coordinating several
 * components.
class ConcreteMediator implements Mediator {
    private component1: Component1;

    private component2: Component2;

    constructor(c1: Component1, c2: Component2) {
        this.component1 = c1;
        this.component2 = c2;

    public notify(sender: object, event: string): void {
        if (event === 'A') {
            console.log('Mediator reacts on A and triggers following operations:');

        if (event === 'D') {
            console.log('Mediator reacts on D and triggers following operations:');

 * The Base Component provides the basic functionality of storing a mediator's
 * instance inside component objects.
class BaseComponent {
    protected mediator: Mediator;

    constructor(mediator?: Mediator) {
        this.mediator = mediator!;

    public setMediator(mediator: Mediator): void {
        this.mediator = mediator;

 * Concrete Components implement various functionality. They don't depend on
 * other components. They also don't depend on any concrete mediator classes.
class Component1 extends BaseComponent {
    public doA(): void {
        console.log('Component 1 does A.');
        this.mediator.notify(this, 'A');

    public doB(): void {
        console.log('Component 1 does B.');
        this.mediator.notify(this, 'B');

class Component2 extends BaseComponent {
    public doC(): void {
        console.log('Component 2 does C.');
        this.mediator.notify(this, 'C');

    public doD(): void {
        console.log('Component 2 does D.');
        this.mediator.notify(this, 'D');

 * The client code.
const c1 = new Component1();
const c2 = new Component2();
const mediator = new ConcreteMediator(c1, c2);

console.log('Client triggers operation A.');

console.log('Client triggers operation D.');

Output.txt: Execution result

Client triggers operation A.
Component 1 does A.
Mediator reacts on A and triggers following operations:
Component 2 does C.

Client triggers operation D.
Component 2 does D.
Mediator reacts on D and triggers following operations:
Component 1 does B.
Component 2 does C.

Mediator in Other Languages

Mediator in C# Mediator in C++ Mediator in Go Mediator in Java Mediator in PHP Mediator in Python Mediator in Ruby Mediator in Rust Mediator in Swift