Patterns

Externalized Configuration

architectural cross-cutting best practice

The Externalized Configuration pattern separates application configuration data from the application’s code. Instead of hardcoding configuration values within the code, these values are stored in external sources like configuration files, databases, environment variables, or dedicated configuration servers. This …

Facade

creational structural

The Facade pattern provides a simplified interface to a complex system of classes, objects, and subsystems. It abstracts away the intricacies of the underlying components, offering clients a higher-level, easier-to-use entry point. Essentially, it’s an “entry point” object that encapsulates the interaction …

Feature Toggle

behavioral development release

The Feature Toggle (also known as Feature Flag) pattern allows the modification of application behavior without requiring a deployment. It essentially involves wrapping a section of code within a conditional statement controlled by a toggle. This toggle can be dynamically switched at runtime, enabling or disabling a …

Fire-and-Forget

concurrent behavioral

The Fire-and-Forget pattern is a style of concurrency where a task is submitted to an executor and the calling code does not wait for the task to complete. It’s often used when invoking an asynchronous operation and the result of that operation isn’t immediately needed or is handled elsewhere. Essentially, you …

Flux

architectural behavioral reactive

Flux is an application architecture for managing the state of a web application. It’s commonly used with React and other JavaScript frameworks, but the principles can be applied more broadly. The core idea is unidirectional data flow: data flows in a single direction, making it easier to reason about and debug …

Fork-Join

concurrency behavioral

The Fork-Join pattern is a parallel programming strategy that recursively breaks down a problem into smaller, independent subtasks. These subtasks are then executed concurrently, often on different processors or threads. Finally, the results from these subtasks are combined (joined) to produce the overall solution. …

Future

behavioral asynchronous

The Future pattern encapsulates the result of an asynchronous computation. Instead of blocking the calling thread while waiting for the result, a Future object provides a placeholder. The client can then query the Future for the availability of the result and retrieve it when it’s ready, potentially doing other …

Hexagonal Architecture

architectural DDD

The Hexagonal Architecture (also known as Ports and Adapters) is a software design pattern that aims to create loosely coupled software applications with a clear separation of concerns. The core business logic is kept independent of external technologies like databases, UI frameworks, or messaging systems. This is …

HMVC

behavioral web

HMVC (Hierarchical Model-View-Controller) is a web application design pattern that structures a web application into three interconnected parts: the Model (data), the View (user interface), and the Controller (application logic). It expands on the traditional MVC pattern by allowing views to be controllers, and …

Immutable Object

creational best practice

An Immutable Object is an object whose state cannot be modified after it is created. Any operation that appears to modify the object actually returns a new object with the desired changes, leaving the original object untouched. This is achieved by making all of the object’s fields final (or equivalent) and …