Patterns

Rolling Deployment

Rolling deployment is a software deployment strategy where new versions of an application are released to a subset of users or servers at a time, rather than all at once. This approach minimizes downtime and reduces the risk of widespread issues by allowing for gradual rollout and monitoring. If problems are detected, …

Splitter

behavioral processing

The Splitter pattern addresses the need to divide a larger data chunk (often a string) into smaller, manageable pieces based on a defined delimiter or strategy. It decouples the splitting logic from the code that consumes the split data, enabling flexibility and maintainability when splitting rules evolve or differ …

Geo-Replication

distributed systems scalability reliability

Geo-Replication is a technique used to distribute data across multiple geographically diverse locations. This is done to improve performance for users in those regions (by reducing latency), increase availability and fault tolerance (by having backups in different locations), and provide disaster recovery capabilities. …

Module

structural software architecture

The Module pattern is a structural design pattern that aims to reduce the complexity of a software system by dividing it into independent, interchangeable modules. Each module encapsulates a specific set of related functionalities, offering a well-defined interface to interact with other parts of the system. This …

Event-Carried State Transfer

behavioral integration DDD

The Event-Carried State Transfer pattern focuses on transferring state between components using events. Instead of directly exposing and modifying an object’s state, a component publishes an event that contains a complete snapshot of the state to be transferred as a Value Object (or Transfer Object). Another …

Durable Subscriber

behavioral message-queue

The Durable Subscriber pattern addresses the reliability of message consumption in messaging systems. It ensures that a subscriber receives all messages published to a topic, even if the subscriber is temporarily offline or disconnects. This is achieved by persistently storing messages intended for the subscriber …

Open Host Service

architectural integration scalability

The Open Host Service pattern addresses the need for exposing functionality or data from an internal system (the Host) to external services (the Service) in a controllable and scalable way. It acts as an intermediary, preventing direct access to the Host and offering a standardized interface. This separation of …

Read Model

CQRS behavioral data

The Read Model pattern addresses the performance challenges of querying complex domains by maintaining one or more specialized data stores optimized for specific read operations. Instead of directly querying the primary data store (often an event store or normalized database used by the write side), the read model …

Expand-Contract

behavioral DDD

The Expand-Contract pattern addresses scenarios where an object’s behavior needs to be dynamically altered by adding or removing components. It’s particularly useful when dealing with complex functionality that isn’t always required, promoting a lean initial state and deferring the instantiation of …

Conformist

behavioral integration

The Conformist pattern focuses on integrating with a pre-existing system or interface, even if that interface is poorly designed or doesn’t fully meet the needs of the integrating component. It prioritizes compatibility and “fitting in” over ideal design principles, often acting as a wrapper or translator to …