Patterns

Point-to-Point Channel

The Point-to-Point Channel pattern facilitates direct, synchronous or asynchronous communication between two specific endpoints. It ensures that a message sent from one point is delivered to and processed by exactly one other point. This provides a focused communication pathway, differing from publish-subscribe models …

Presentation Model

behavioral UI

The Presentation Model pattern dictates a clear separation between the data and business logic of an application, and the UI layer responsible for displaying it. The Presentation Model acts as an intermediary, exposing data specifically tailored for the View. It abstracts the complexities of the underlying data and …

Producer-Consumer

concurrency behavioral

The Producer-Consumer pattern decouples the production of data from its consumption, enabling concurrent processing. A ‘producer’ creates data and places it into a shared buffer (typically a queue), while one or more ‘consumers’ retrieve and process that data. This separation allows producers …

Prototype

creational object-creation

The Prototype pattern is a creational design pattern that empowers you to create new objects by cloning existing ones, offering a flexible alternative to traditional instantiation methods. Instead of specifying new object creation through classes, it delegates the creation responsibility to a prototype instance. This …

Publish-Subscribe

behavioral messaging

The Publish-Subscribe pattern defines one-to-many dependencies between objects. A publisher (or event source) doesn’t know about its subscribers. Instead, it publishes events to a broker (or message queue), and subscribers express interest in specific events by registering with the broker. When an event occurs, the …

Publish-Subscribe Channel

behavioral messaging event-driven

The Publish-Subscribe Channel pattern decouples message senders (Publishers) from message receivers (Subscribers) by introducing a message channel. Publishers don’t need to know which Subscribers are interested in the messages, and Subscribers don’t need to know who is publishing the messages. Instead, Publishers send …

Published Language

behavioral integration

The Published Language pattern allows components to communicate without tight coupling by using a central event bus or topic. A ‘Publisher’ emits events in a specific ‘Language’ (essentially, the structure and meaning of the event data) without needing to know who the ‘Subscribers’ …

Read-Write Lock

concurrency behavioral

The Read-Write Lock pattern allows multiple readers to access a shared resource concurrently, but requires exclusive access for writers. This is in contrast to a traditional mutex, which only allows one thread to access the resource at a time, regardless of whether it’s reading or writing. By allowing concurrent …

Replication

distributed systems reliability scalability

The Replication pattern addresses the need for data consistency and availability across multiple systems. It involves creating and maintaining multiple copies of data, ensuring that if one copy fails, others are available to serve requests. This enhances fault tolerance, improves read performance by distributing load, …

Repository

DDD behavioral

The Repository pattern provides an abstraction layer between the domain logic and the data access layer. It encapsulates the complexities of data access, allowing the domain to work with objects without knowing how they are stored or retrieved. This promotes loose coupling, making the application easier to test, …