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. …

Read More

Infrastructure as Code (IaC) is the practice of managing and provisioning infrastructure through code, rather than through manual processes. This means that infrastructure – servers, virtual machines, networks, load balancers, databases, etc. – is treated as code, stored in version control, and automated through …

Read More

Self-Contained Systems is an architectural pattern where an application is structured as a suite of independently deployable services, each with its own database and logic. These systems are designed to be loosely coupled, communicating with each other via well-defined APIs, but without sharing databases or internal …

Read More

The Application Service pattern defines a layer responsible for coordinating the execution of use cases within a domain-driven design (DDD) application. It acts as an intermediary between the presentation layer (UI, API) and the domain layer, encapsulating the application’s behavior and orchestrating domain …

Read More

The Policy pattern encapsulates a set of business rules or logic into separate classes, allowing for greater flexibility and maintainability. It defines a family of algorithms (policies) and makes them interchangeable, enabling the selection of the appropriate algorithm at runtime based on context. Rather than …

Read More

The Database per Service pattern dictates that each microservice should have its own dedicated database. This contrasts with a shared database approach where multiple services access a single database, which is a common anti-pattern in microservice architectures. The key principle is to decouple data storage from the …

Read More

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 …

Read More

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 …

Read More

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 …

Read More

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 …

Read More