Behavioral Patterns

Retry with Backoff

The Retry with Backoff pattern is a resilience strategy that automatically retries a failed operation after waiting for an increasing amount of time. This is particularly useful when dealing with transient failures, such as network glitches, temporary service unavailability, or resource contention. The …

Master-Slave

behavioral concurrency

The Master-Slave pattern is a concurrency model where one thread (the master) distributes work to multiple other threads (slaves). The master thread typically manages the tasks, assigns them to available slaves, and aggregates the results. Slaves operate independently, processing their assigned tasks without direct …

Null Object

behavioral

The Null Object pattern provides a substitute for a missing or undefined object. Instead of returning null or throwing an exception when an object is not available, a null object is returned. This null object implements the expected interface without any concrete behavior, effectively doing nothing. This simplifies …

Load Shedding

reliability resilience behavioral

Load shedding is a mechanism for gracefully handling overload situations in a system. When demand exceeds available resources (CPU, memory, network, database connections, etc.), a load shedding strategy is employed to selectively reject or delay requests, preventing the system from complete failure. It prioritizes …

Service Discovery

behavioral distributed systems

Service Discovery is a pattern used in distributed systems to enable services to locate each other dynamically. In a microservices architecture, the number of services, their locations, and instances can change frequently. Service Discovery addresses this challenge by providing a mechanism for services to register …

Resequencer

behavioral data

The Resequencer pattern addresses the problem of ensuring events are processed in the correct order when dealing with distributed systems or asynchronous processing where event delivery order is not guaranteed. It acts as an intermediary, buffering and reordering events based on a defined sequence identifier before …

Outbox Pattern

behavioral integration reliability

The Outbox Pattern addresses the challenge of reliably publishing events in a transactional context. When an application modifies its data and needs to publish an event to notify other services, ensuring both operations occur atomically is crucial. Directly publishing events from the application can lead to eventual …

Application Controller

behavioral web

The Application Controller pattern centralizes request handling logic within a dedicated controller class. It receives all incoming requests, coordinates the necessary actions to fulfill those requests (potentially involving multiple other objects or components), updates the application model, selects the appropriate …

Partnership

behavioral DDD

The Partnership pattern defines a relationship between two or more independent entities (Partners) who collaborate to achieve a common goal through a shared state. Each Partner maintains its own autonomy but relies on the SharedState for synchronization and data exchange, effectively creating a bounded collaboration. …

Half-Sync/Half-Async

behavioral concurrency

The Half-Sync/Half-Async pattern addresses performance bottlenecks in request processing by decoupling time-consuming, non-essential tasks from the critical path. It allows a service to respond quickly to a client by handling essential parts of a request synchronously, then offloading less important, potentially …