Behavioral Patterns

HMVC

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 …

Inbox Pattern

behavioral integration

The Inbox Pattern is a technique for decoupling message producers from message consumers in a system. It introduces an inbox component that acts as a central point for receiving messages. Producers simply send messages to the inbox, without needing to know about or directly interact with the consumers. The inbox then …

Iterator

behavioral design patterns

The Iterator pattern is a behavioral design pattern that provides a way to access the elements of an aggregate object (like a list, set, or tree) sequentially without exposing its underlying representation. It defines a standard interface for creating iterators, allowing clients to traverse and manipulate elements …

Log Aggregation

behavioral observability distributed systems

Log Aggregation is a technique for collecting logs from multiple sources – applications, servers, network devices, etc. – in a centralized location. This allows for easier analysis, monitoring, and troubleshooting of complex systems. Instead of having to access individual machines to investigate issues, this pattern …

Memento

behavioral

The Memento pattern allows saving and restoring an object’s internal state without violating encapsulation. It achieves this by creating a separate “memento” object that holds the state, which the originator can create and hand to a caretaker for storage. The caretaker is responsible for holding …

Message Broker

behavioral integration distributed systems

The Message Broker pattern facilitates communication and data exchange between different applications, systems, and services. It acts as an intermediary, receiving messages from producers and routing them to interested consumers. This decoupling allows components to operate independently, improving scalability, …

Message Dispatcher

behavioral event-driven

The Message Dispatcher pattern decouples the sender of a message (or event) from its receiver(s). A central dispatcher component receives messages and routes them to the appropriate handler(s) based on message type or content. This promotes loose coupling, allowing new handlers to be added without modifying the …

Message Filter

behavioral middleware

The Message Filter pattern involves defining multiple handlers, each responsible for processing a specific type of message. A filter component receives a message and iterates through the handlers, forwarding it to the first handler that accepts it. If no handler accepts the message, it’s passed to a default …

Message Router

behavioral integration

The Message Router pattern is a behavioral pattern that centralizes the control of message distribution within a system. It receives messages from clients and routes them to the appropriate handler(s) based on message type, content, or other defined criteria. This promotes loose coupling, allowing clients to send …

MVC

behavioral architectural

The Model-View-Controller (MVC) pattern is a widely used architectural pattern for developing user interfaces. It divides an application into three interconnected parts: the Model, which manages the application’s data and logic; the View, which displays the data to the user; and the Controller, which handles user …