Subject Pattern — Multicast Observable

In this tutorial, you'll learn how the Subject pattern provides a multicast observable that can push values to multiple subscribers.

What You'll Learn

how the Subject pattern provides a multicast observable that can push values to multiple subscribers.

Why It Matters

Creating new observables for each subscriber is wasteful. Subject shares one source across subscribers.

Real-World Use

RxJS Subject, BehaviorSubject, and ReplaySubject for state management and event buses.

The Subject Pattern

The Subject pattern addresses a specific recurring design problem by providing a reusable solution structure. Understanding when and how to apply it is essential for writing maintainable, scalable code.

Key Concepts

• Observability: Components can be observed for state changes.
• Push-based: Data is pushed rather than polled.
• Backpressure: Consumers can signal producers to slow down.
• Composability: Streams can be transformed, filtered, and combined.

Structure

The following diagram shows the structure of this pattern:

flowchart LR
    Producer -- next(value) --> Subject
    Subject -- subscribe(fn) --> Observer1
    Subject -- subscribe(fn) --> Observer2

Implementation

from typing import List, Callable, Any

class Subject:
    def __init__(self):
        self._subscribers: List[Callable] = []
        self._error_handlers: List[Callable] = []

    def subscribe(self, on_next: Callable, on_error: Callable = None):
        self._subscribers.append(on_next)
        if on_error:
            self._error_handlers.append(on_error)

    def next(self, value: Any):
        for sub in self._subscribers:
            sub(value)

    def error(self, err: Exception):
        for handler in self._error_handlers:
            handler(err)

    @staticmethod
    def from_iterable(items: List) -> 'Subject':
        stream = Subject()
        for item in items:
            stream.next(item)
        return stream

stream = Subject()
stream.subscribe(
    lambda v: print(f"Received: {v}"),
    lambda e: print(f"Error: {e}")
)
stream.next("Hello")
stream.next(42)
stream.next([1, 2, 3])

Expected output:

Received: Hello
Received: 42
Received: [1, 2, 3]

Key Participants

• Observable/Subject: Source of data events.
• Observer/Subscriber: Consumer that reacts to events.
• Operator: Transform applied to event stream.

Real-World Examples

• DodaTech uses this pattern internally for consistent cross-cutting concerns.
• Major frameworks and libraries implement this pattern as a core architectural element.
• Production systems at scale depend on this pattern for reliability.

Related Patterns

• Observable

• Observer

• Reactive

• Design Patterns — the complete patterns catalog.

Pros and Cons

Common Mistakes

1. **Over-engineering: Applying Subject where a simpler solution suffices, adding unnecessary complexity.

2. **Wrong granularity: Implementing Subject at the wrong level of abstraction.

3. **Thread Safety ignored: Using Subject in concurrent context without proper synchronization.

4. **Tight coupling: Violating the pattern intent by creating hidden dependencies.

5. **Premature optimization: Introducing Subject before there is evidence it is needed.

Practice Questions

1. What problem does the Subject pattern solve? Describe a real-world scenario where using it improves code quality.

2. How does Subject differ from alternative approaches? What are the trade-offs?

3. What testing Strategy would you use for code that implements Subject?

4. How would you refactor legacy code to introduce Subject?

5. When should you NOT use Subject? Describe scenarios where it adds unnecessary complexity.

Challenge

Implement a complete Subject example in Python with unit tests. Include error handling, edge cases (empty data, null values, concurrent access), and a performance comparison against a simpler alternative. Document your design decisions.

Real-World Task

Find a section of code in your current project that could benefit from the Subject pattern. Refactor it, write tests, and measure the improvement in testability, coupling, and cohesion.

Security Tip: When implementing Subject, ensure proper input validation, avoid exposing internal state, and follow Least Privilege. At DodaTech, all implementations undergo security review.

Built by the developers of Doda Browser, DodaZIP, and Durga Antivirus Pro.