Behavioral Patterns

MVP

The Model-View-Presenter (MVP) pattern is a user interface architectural pattern that originated from a desire to improve the separation of concerns in graphical user interface (GUI) development. It’s similar to Model-View-Controller (MVC), but with a key difference: the View in MVP is entirely passive, …

MVVM

architectural behavioral

MVVM (Model-View-ViewModel) is an architectural pattern that facilitates the separation of an application’s concerns – data presentation (View), interaction logic (ViewModel), and data management (Model). It’s primarily used in conjunction with data binding, allowing automatic synchronization of data between the …

Page Controller

behavioral web

The Page Controller pattern is a simple and straightforward approach to handling user requests in web applications. It centralizes request handling logic within a controller, which is responsible for determining which data needs to be fetched, preparing the data, selecting the appropriate view, and rendering the final …

Pipes and Filters

behavioral data processing

The Pipes and Filters pattern is a data processing paradigm where a series of independent processing components (Filters) are connected by channels (Pipes). Each Filter performs a specific transformation on the input data and passes the result to the next Filter in the pipeline. The pattern promotes modularity, …

Point-to-Point Channel

behavioral messaging

The Point-to-Point Channel pattern facilitates direct, synchronous or asynchronous communication between two specific endpoints. It ensures that a message sent from one point is delivered to and processed by exactly one other point. This provides a focused communication pathway, differing from publish-subscribe models …

Presentation Model

behavioral UI

The Presentation Model pattern dictates a clear separation between the data and business logic of an application, and the UI layer responsible for displaying it. The Presentation Model acts as an intermediary, exposing data specifically tailored for the View. It abstracts the complexities of the underlying data and …

Producer-Consumer

concurrency behavioral

The Producer-Consumer pattern decouples the production of data from its consumption, enabling concurrent processing. A ‘producer’ creates data and places it into a shared buffer (typically a queue), while one or more ‘consumers’ retrieve and process that data. This separation allows producers …

Publish-Subscribe

behavioral messaging

The Publish-Subscribe pattern defines one-to-many dependencies between objects. A publisher (or event source) doesn’t know about its subscribers. Instead, it publishes events to a broker (or message queue), and subscribers express interest in specific events by registering with the broker. When an event occurs, the …

Publish-Subscribe Channel

behavioral messaging event-driven

The Publish-Subscribe Channel pattern decouples message senders (Publishers) from message receivers (Subscribers) by introducing a message channel. Publishers don’t need to know which Subscribers are interested in the messages, and Subscribers don’t need to know who is publishing the messages. Instead, Publishers send …

Published Language

behavioral integration

The Published Language pattern allows components to communicate without tight coupling by using a central event bus or topic. A ‘Publisher’ emits events in a specific ‘Language’ (essentially, the structure and meaning of the event data) without needing to know who the ‘Subscribers’ …