What is Observer Pattern?

What Is the Observer Pattern?

The Observer pattern is a behavioral design pattern where one object automatically notifies subscribed objects when its state changes. The object holding the state is often called the subject or publisher; the objects that react are observers or subscribers.

The pattern reduces direct coupling between objects. The subject does not need to know how each observer handles the change. It only announces the event; sending an email, updating a screen, or clearing a cache remains the observer’s responsibility.

How It Works

1. An observer interface defines an update-style method.
2. The subject keeps a list of observers and exposes subscribe/unsubscribe methods.
3. When the subject’s state changes, it notifies every observer in the list.
4. Each observer handles the notification in its own way.

Frontend state management, DOM events, messaging systems, domain event listeners, and notification infrastructure all use variations of this idea. JavaScript’s event listener model is a familiar everyday example.

Business Use

When an order changes to “shipped”, the same event can trigger a customer SMS, an inventory update in reporting, and an accounting record. The order module does not need to know the details of every downstream integration.

The Observer pattern is a core example in the design pattern family and shares the same mindset as event-driven architecture. If overused, event chains can become hard to follow, so monitoring, error handling, and subscription cleanup are important.