Architectural Patterns

The Health Check Endpoint pattern provides a way to expose an endpoint that reports the overall health and status of an application or service. This endpoint allows external systems, such as load balancers, monitoring tools, and other services, to determine if the application is running and able to handle requests. …

Read More

Redux is a predictable state container for JavaScript apps. It helps you manage your application’s state in a centralized and organized manner, making it easier to debug, test, and reason about your application’s behavior. The core idea is to keep the application’s state in a single, immutable store, and only …

Read More

The Backend for Frontend (BFF) pattern addresses the complexities of building client applications that consume multiple backend services, particularly in microservice architectures. It involves creating a separate backend layer specifically tailored to the needs of each client type (e.g., web, mobile, smartwatch). …

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 Layered Architecture pattern organizes an application into distinct layers, each with a specific role and responsibility. Layers are arranged hierarchically, with each layer building upon the services provided by the layer below. This separation promotes modularity, maintainability, and testability by reducing …

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

Immutable infrastructure is a practice where servers are never modified after they’re provisioned. Instead, if a change is required, a new server is provisioned with the updated configuration, and the old server is replaced. This approach treats infrastructure as code, emphasizing version control and repeatability. It …

Read More

The Config Server pattern centralizes configuration management for distributed systems, particularly microservices. Instead of embedding configuration directly within applications or duplicating it across various deployment environments, a dedicated Config Server acts as a single source of truth. Client applications …

Read More

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 More

The Anti-Corruption Layer (ACL) is an architectural pattern used to isolate a core application from problematic or poorly understood external systems (often legacy systems). It acts as a translation layer, preventing the complexities, inconsistencies, and potential errors of the external system from polluting the …

Read More