Behavioral Patterns

Actor Model

The Actor Model is a concurrent computation model that treats “actors” as the fundamental units of computation. Actors encapsulate state and behavior, and communicate with each other exclusively through asynchronous message passing. This avoids the complexities of shared mutable state and locks, leading to …

Unit of Work

behavioral DDD

The Unit of Work pattern is a mechanism to manage a sequence of operations against a data store as a single logical unit. It encapsulates all changes made to persistent objects within a single transaction, ensuring that either all changes are applied successfully, or none are. This is crucial for maintaining data …

Ambassador

behavioral microservices distributed systems

The Ambassador pattern provides a single point of entry for a system (or set of backend services) while abstracting away the internal complexity. It acts as a forward-facing proxy that handles requests, potentially transforming them, adding security, and routing them to the appropriate backend. This decouples clients …

Lazy Load

behavioral performance

Lazy Load is a design pattern used in computer programming to delay the initialization of an object until the point at which it is first used. Instead of loading resources or creating objects upfront, the pattern postpones these operations to improve initial load times and conserve system resources. This is …

Value Object

DDD behavioral

A Value Object is an object that describes some characteristic of a Domain, but has no concept of identity. Instead of being defined by its unique position in memory (like an Entity), it is defined by the values it holds. Two Value Objects with the same values are considered equal, and are interchangeable. They are …

Active Object

concurrency behavioral

The Active Object pattern provides a way to decouple method execution from method invocation. It introduces a separate object (the Active Object) responsible for managing all method requests and executing them within its own thread, avoiding complexities and potential issues with direct thread management by client …

Adapter Container

behavioral integration

The Adapter Container pattern addresses integration challenges when a client requires a service through a specific interface, but the available service provides a different, incompatible interface. This pattern encapsulates the legacy service within an adapter, translating requests from the client’s interface to the …

Aggregate Root

DDD behavioral

The Aggregate Root pattern is a core concept in Domain-Driven Design (DDD) used to define transactional consistency boundaries. It designates a specific entity within a cluster of associated objects (the aggregate) as the single point of access for modifying the aggregate’s state. This root is responsible for ensuring …

Aggregator

behavioral integration

The Aggregator pattern provides a unified interface to a number of disparate subsystems. Instead of a client having to interact with each subsystem directly, it interacts with the aggregator, which then dispatches requests to the appropriate subsystems. The aggregator then combines the results from these subsystems …

Balking

behavioral state

The Balking pattern is a behavioral pattern that allows an object to postpone the execution of a request until a specific condition is met. It essentially prevents an object from performing an action if it’s already in a particular state, often a “busy” or “occupied” state. This is …