Also known as

• Flow Control
• Rate Limiting Mechanism

Intent of the Backpressure Design Pattern

Control the rate of data production so downstream consumers are not overwhelmed by excessive load.

Detailed Explanation of Backpressure Pattern with Real-World Examples

Also known as

• Business Logic Component
• Business Logic Controller

Intent of the Bloc Pattern

The Bloc pattern manages the state of an object and allows for dynamically notifying interested listeners about state changes. It separates state management logic from the rest of the application, improving code organization and flexibility.

Also known as

• Chain of Command
• Chain of Objects
• Responsibility Chain

Intent of Chain of Responsibility Design Pattern

The Chain of Responsibility pattern in Java is a behavioral design pattern that decouples the sender of a request from its receivers by giving more than one object a chance to handle the request. The receiving objects are chained and the request is passed along the chain until an object handles it.

Also known as

• CQRS

Intent of Command Query Responsibility Segregation Design Pattern

Command Query Responsibility Segregation (CQRS) aims to segregate the operations that modify the state of an application (commands) from the operations that read the state (queries). This separation enhances scalability, performance, and maintainability in complex software systems.

Also known as

• Event Bus
• Message Bus

Intent of Data Bus Design Pattern

The Data Bus design pattern aims to provide a centralized communication channel through which various components of a system can exchange data without being directly connected, thus promoting loose coupling and enhancing scalability and maintainability.

Also known as

• Event Channel
• Event Central
• Message Hub

Intent of Event Aggregator Design Pattern

An Event Aggregator is a design pattern used for handling events in a system. It centralizes the event handling logic, making it easier to manage and maintain. The Event Aggregator design pattern aims to decouple event generation from event handling. This design pattern collects events from multiple sources and routes them to the appropriate handlers.

Also known as

• Asynchronous Event Handling

Intent of Event-Based Asynchronous Design Pattern

The Event-Based Asynchronous pattern allows a system to handle tasks that might take some time to complete without blocking the execution of the program. It enables better resource utilization by freeing up a thread that would otherwise be blocked waiting for the task to complete.

Also known as

• Event-Driven System
• Event-Based Architecture

Intent of Event-Driven Architecture Design Pattern

Event-Driven Architecture (EDA) is designed to orchestrate behavior around the production, detection, consumption of, and reaction to events. This architecture enables highly decoupled, scalable, and dynamic interconnections between event producers and consumers.

Also known as

• Event Stream
• Message Queue

Intent of Event Queue Design Pattern

The Event Queue pattern is designed to manage tasks in an asynchronous manner, allowing applications to handle operations without blocking user interactions or other processes. This improves scalability and system performance.

Also known as

• Event Logging
• Event Streaming

Intent of Event Sourcing Design Pattern

Event Sourcing is a design pattern that advocates for the storage of state changes as a sequence of events. Instead of updating a record in a database, all changes are stored as individual events which, when replayed, can recreate the state of an application at any point in time.