Resequencer Pattern — Reorder Out-of-Sequence Messages

In this tutorial, you'll learn how the Resequencer pattern reorders messages that arrive out of sequence back to the correct order.

What You'll Learn

how the Resequencer pattern reorders messages that arrive out of sequence back to the correct order.

Why It Matters

Parallel processing delivers results out of order. Resequencer restores correct message sequence.

Real-World Use

Apache Camel resequencer, Mule batch processor, and Kafka Compacted topics.

The Resequencer Pattern

The Resequencer 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

• Message Routing: Resequencer directs messages from producers to consumers.
• Transformation: Converts message formats between systems.
• Decoupling: Producers and consumers have no direct knowledge of each other.
• Reliability: Ensures delivery even when components fail.

Structure

The following diagram shows the structure of this pattern:

flowchart LR
    Producer -- Message --> Resequencer
    Resequencer -- Route --> ConsumerA
    Resequencer -- Route --> ConsumerB

Implementation

from typing import List, Dict
from dataclasses import dataclass

@dataclass
class Message:
    key: str
    payload: str

class Resequencer:
    def __init__(self):
        self._subscribers: Dict[str, List] = {}

    def subscribe(self, key: str, handler):
        self._subscribers.setdefault(key, []).append(handler)

    def publish(self, msg: Message):
        handlers = self._subscribers.get(msg.key, [])
        for h in handlers:
            h(msg)

def log_handler(msg: Message):
    print(f"LOG: {msg.key} -> {msg.payload}")

def alert_handler(msg: Message):
    print(f"ALERT: {msg.key} -> {msg.payload.upper()}")

bus = Resequencer()
bus.subscribe("order.created", log_handler)
bus.subscribe("order.created", alert_handler)
bus.subscribe("order.shipped", log_handler)

bus.publish(Message("order.created", "Order #1234"))
print("---")
bus.publish(Message("order.shipped", "Order #5678"))

Expected output:

LOG: order.created -> Order #1234
ALERT: order.created -> ORDER #1234
---
LOG: order.shipped -> Order #5678

Key Participants

• Producer: Component that sends messages.
• Consumer: Component that receives messages.
• Resequencer: Routes and transforms messages.
• Channel: Medium through which messages flow.

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

• Splitter

• Aggregator

• Routing Slip

• Design Patterns — the complete patterns catalog.

Pros and Cons

Common Mistakes

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

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

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

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

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

Practice Questions

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

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

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

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

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

Challenge

Implement a complete Resequencer 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 Resequencer pattern. Refactor it, write tests, and measure the improvement in testability, coupling, and cohesion.

Security Tip: When implementing Resequencer, 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.