Proactor Pattern — Asynchronous Completion Dispatching

In this tutorial, you'll learn how the Proactor pattern initiates asynchronous operations and dispatches completion events to completion handlers.

What You'll Learn

how the Proactor pattern initiates asynchronous operations and dispatches completion events to completion handlers.

Why It Matters

Reactor requires the handler to start the operation. Proactor initiates and handles completion separately.

Real-World Use

Windows I/O Completion Ports, Boost.Asio proactor, and Java AsynchronousSocketChannel.

The Proactor Pattern

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

• Synchronization: Proactor coordinates access to shared resources.
• Contention Management: Limits concurrent access to prevent exhaustion.
• Thread Safety: Ensures correct behavior under concurrent execution.
• Deadlock Prevention: Avoids circular wait conditions.

Structure

The following diagram shows the structure of this pattern:

stateDiagram-v2
    [*] --> Idle
    Idle --> Acquired : acquire()
    Acquired --> Busy : executing
    Busy --> Idle : release()
    Idle --> [*]

Implementation

import threading
import time
from typing import List

class Proactor:
    def __init__(self, max_workers: int = 4):
        self._max = max_workers
        self._active = 0
        self._lock = threading.Lock()

    def acquire(self, worker_id: int):
        with self._lock:
            if self._active < self._max:
                self._active += 1
                print(f"Worker {worker_id}: acquired ({self._active}/{self._max} active)")
                return True
            print(f"Worker {worker_id}: rejected ({self._active}/{self._max} active)")
            return False

    def release(self, worker_id: int):
        with self._lock:
            self._active -= 1
            print(f"Worker {worker_id}: released ({self._active}/{self._max} active)")

pool = Proactor(2)
def task(wid):
    if pool.acquire(wid):
        time.sleep(0.1)
        pool.release(wid)

threads = [threading.Thread(target=task, args=(i,)) for i in range(4)]
for t in threads: t.start()
for t in threads: t.join()

Expected output:

Worker 0: acquired (1/2 active)
Worker 1: acquired (2/2 active)
Worker 2: rejected (2/2 active)
Worker 3: rejected (2/2 active)
Worker 0: released (1/2 active)
Worker 1: released (0/2 active)
Worker 2: acquired (1/2 active)
Worker 3: acquired (2/2 active)
Worker 2: released (1/2 active)
Worker 3: released (0/2 active)

Key Participants

• Resource: The shared resource being protected.
• Worker: Thread that requests access.
• Proactor: Manages access control and synchronization.

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

• Reactor

• Leader Followers

• Active Object

• Design Patterns — the complete patterns catalog.

Pros and Cons

Common Mistakes

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

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

3. **Thread safety ignored: Using Proactor in concurrent context without proper synchronization.

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

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

Practice Questions

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

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

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

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

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

Challenge

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

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