Patterns

Worker Thread

The Worker Thread pattern addresses the need to perform potentially long-running or blocking operations without freezing the main thread of an application, ensuring a responsive user interface or continued service availability. It achieves this by delegating work to a pool of worker threads that operate concurrently, …

Process Manager

behavioral concurrency

The Process Manager pattern provides a centralized point of control for managing and executing potentially long-running or complex tasks. It decouples the task submission from the actual task execution, allowing for features like queuing, prioritization, resource management (such as thread pools), and monitoring of …

Fallback

behavioral resilience

The Fallback pattern provides a secondary mechanism to fulfill a request when the primary attempt fails. It’s a key component in building resilient systems, ensuring continued operation even in the face of partial failures. This pattern doesn’t actively prevent failure, but gracefully handles it by …

Domain Service

DDD behavioral

The Domain Service pattern encapsulates complex domain logic that doesn’t naturally belong to any specific entity or value object. It serves as a central point for operations that involve multiple entities or intricate business rules, preventing these behaviors from cluttering up the domain model. This keeps entities …

Shared Database

behavioral architectural

The Shared Database pattern describes a situation where multiple clients or applications access the same underlying database. This allows for data consistency and simplifies data sharing between different parts of a system. The primary benefit is avoiding data duplication and potential synchronization issues when many …

Fluent Interface

behavioral idiomatic

The Fluent Interface pattern enables the creation of readable and maintainable code by allowing method calls to be chained together. It achieves this by making methods return the object itself (or another builder object) instead of void. This results in a more natural and expressive syntax for configuring or building …

Saga (Orchestration)

distributed system behavioral integration

The Saga pattern manages a sequence of local transactions in a distributed system. It’s used to ensure data consistency across multiple services, especially when traditional ACID transactions aren’t feasible due to the nature of distributed environments. Instead of a single, atomic transaction, the Saga …

Sidecar

architectural system

The Sidecar pattern involves deploying a secondary process (the “sidecar”) alongside a primary application in a supporting role. This sidecar is typically in a separate container but shares the same lifecycle as the main application, and it enhances the main application with functionality like logging, monitoring, …

Promise

behavioral asynchronous

The Promise pattern addresses the complexities of asynchronous operations in programming. It provides a placeholder for a value that will be available at some point in the future, without blocking the current execution thread. Instead of directly handling the result or error of an operation, a Promise offers a clean …

Query Object

behavioral data access

The Query Object pattern encapsulates complex data retrieval logic into dedicated objects. Instead of scattering database or service queries throughout your application’s logic, you move them into these query objects. This promotes separation of concerns, making your domain models cleaner and more focused on their core …