Design Patterns in JavaScript: An Overview with Examples

Design patterns are proven solutions to common problems that developers face in their everyday programming tasks. They provide a reusable and efficient way to structure your code and help to prevent the need to reinvent the wheel. In this blog post, we will dive into the world of design patterns in JavaScript and provide an overview with examples, making it beginner-friendly for those who are new to the topic. This guide will cover several popular design patterns, such as Singleton, Factory, Observer, and Strategy, providing clear explanations and code examples to help you understand how they work and how to implement them in your own projects. Furthermore, we will wrap up the blog with a FAQ section, answering some common questions related to design patterns in JavaScript.

Singleton Pattern

The Singleton pattern is a creational design pattern that ensures a class has only one instance, and provides a global point of access to that instance. It's useful when you need to control access to shared resources, such as database connections or configurations.


Here's an example of how to implement the Singleton pattern in JavaScript:

class Singleton { constructor(data) { if (Singleton.instance) { return Singleton.instance; } Singleton.instance = this; = data; } getData() { return; } } const instance1 = new Singleton('Data for instance 1'); const instance2 = new Singleton('Data for instance 2'); console.log(instance1.getData()); // Output: "Data for instance 1" console.log(instance2.getData()); // Output: "Data for instance 1" console.log(instance1 === instance2); // Output: true

In this example, the Singleton class checks if an instance already exists when creating a new object. If it does, the existing instance is returned instead of creating a new one. The getData() method is used to access the data stored in the singleton instance.

Factory Pattern

The Factory pattern is another creational design pattern that provides an interface for creating objects in a super class, but allows subclasses to alter the type of objects that will be created. This pattern is particularly useful when you want to create different types of objects with a common interface, but without specifying the exact class of the object to be created.


Here's an example of how to implement the Factory pattern in JavaScript:

class VehicleFactory { createVehicle(type) { switch (type) { case 'car': return new Car(); case 'motorcycle': return new Motorcycle(); default: throw new Error('Invalid vehicle type'); } } } class Car { drive() { console.log('Driving a car'); } } class Motorcycle { drive() { console.log('Riding a motorcycle'); } } const factory = new VehicleFactory(); const car = factory.createVehicle('car');; // Output: "Driving a car" const motorcycle = factory.createVehicle('motorcycle');; // Output: "Riding a motorcycle"

In this example, the VehicleFactory class has a createVehicle() method that takes a type argument and creates a new object based on that type. The Car and Motorcycle classes both have a drive() method, which is a common interface for all vehicle types.

Observer Pattern

The Observer pattern is a behavioral design pattern that defines a one-to-many dependency between objects. When one object (the subject) changes its state, all dependent objects (observers) are automatically notified and updated.


Here's an example of how to implement the Observer pattern in JavaScript:

class Subject { constructor() { this.observers = []; } addObserver(observer) { this.observers.push(observer); } removeObserver(observer) { const index = this.observers.indexOf(observer); if (index > -1) { this.observers.splice(index, 1); } } notify(data) { this.observers.forEach(observer => observer.update(data)); } } class Observer { update(data) { console.log(`Observer updated with data: ${data}`); } } const subject = new Subject(); const observer1 = new Observer(); const observer2 = new Observer(); subject.addObserver(observer1); subject.addObserver(observer2); subject.notify('New data available'); // Output: // "Observer updated with data: New data available" // "Observer updated with data: New data available"

In this example, the Subject class maintains a list of observers and provides methods to add, remove, and notify them. The Observer class has an update() method that gets called when the subject's state changes. When the notify() method is called on the subject, all registered observers are updated with the new data.

Strategy Pattern

The Strategy pattern is a behavioral design pattern that allows you to define a family of algorithms, encapsulate each one, and make them interchangeable. This pattern is particularly useful when you have multiple ways to perform a specific task and you want to be able to switch between them at runtime.


Here's an example of how to implement the Strategy pattern in JavaScript:

class Context { constructor(strategy) { this.strategy = strategy; } setStrategy(strategy) { this.strategy = strategy; } executeStrategy(data) { return this.strategy.execute(data); } } class LowerCaseStrategy { execute(data) { return data.toLowerCase(); } } class UpperCaseStrategy { execute(data) { return data.toUpperCase(); } } const context = new Context(new LowerCaseStrategy()); console.log(context.executeStrategy('Example Text')); // Output: "example text" context.setStrategy(new UpperCaseStrategy()); console.log(context.executeStrategy('Example Text')); // Output: "EXAMPLE TEXT"

In this example, the Context class maintains a reference to the current strategy and provides methods to set a new strategy and execute it. The LowerCaseStrategy and UpperCaseStrategy classes both implement the execute() method, which defines the specific algorithm to be used.


1. What are design patterns?

Design patterns are reusable, proven solutions to common problems in software design. They provide a shared vocabulary and best practices to help developers write more efficient and maintainable code.

2. Why should I use design patterns in JavaScript?

Using design patterns in JavaScript can help you write more organized, efficient, and maintainable code by providing proven solutions to common problems. They also make your code more readable and easier to understand by other developers.

3. Are design patterns language-specific?

While design patterns are not language-specific, their implementation might vary depending on the language used. Some design patterns are more relevant to specific languages or programming paradigms, but the core concepts can be applied across different languages.

4. When should I use design patterns?

Design patterns should be used when you encounter a problem that has been solved before in a reusable and efficient manner. They can help you avoid reinventing the wheel and save time during the development process.

5. Are there any drawbacks to using design patterns?

Design patterns can sometimes lead to over-engineering or overly complex solutions if not used appropriately. It's essential to understand the problem you're trying to solve and choose the right design pattern for the job.

Sharing is caring

Did you like what Mehul Mohan wrote? Thank them for their work by sharing it on social media.


No comments so far