Patterns
Design patterns relevant to this framework
Mediator Pattern
The Mediator Pattern is a behavioral design pattern that facilitates communication between components or objects by introducing a mediator object. Instead of components communicating directly with each other, they interact through the mediator, which centralizes and manages the interactions. This reduces the dependencies between components, promoting loose coupling and making the system easier to maintain and extend.
flowchart LR
A["Object A"]
B["Object B"]
M["Mediator"]
C["Object C"]
D["Object D"]
A <--> M
B <--> M
M <--> C
M <--> D
classDef mediatorStyle fill:#d9edf7,stroke:#31708f,stroke-width:2px;
class M mediatorStyle;
classDef objectStyle fill:#dff0d8,stroke:#3c763d,stroke-width:2px;
class A,B,C,D objectStyle;
Command Query Responsibility Segregation (CQRS) Pattern
The Command Query Responsibility Segregation (CQRS) Pattern is a design pattern that separates the responsibilities of reading data (queries) and modifying data (commands) into distinct models. This separation allows for optimized handling of read and write operations, enabling scalability, performance improvements, and better maintainability.
flowchart TD
A[Client]
B[Command] --> C[Command Handler]
G[Query] --> H[Query Handler]
F[(Database)]
A -->|Write Side| B
A -->|Read Side| G
C -->|Update| F
H -->|Fetch| F
classDef clientStyle fill:#f0f0f0,stroke:#333,stroke-width:2px;
class A clientStyle;
classDef commandStyle fill:#d9edf7,stroke:#31708f,stroke-width:2px;
class B,G commandStyle;
classDef handlerStyle fill:#dff0d8,stroke:#3c763d,stroke-width:2px;
class C,H handlerStyle;
classDef databaseStyle fill:#f7ecb5,stroke:#8a6d3b,stroke-width:2px;
class F databaseStyle;
References
- https://learn.microsoft.com/en-us/azure/architecture/patterns/cqrs
- https://martinfowler.com/bliki/CQRS.html
Vertical Slice Architecture
The Vertical Slice Architecture is a design approach that structures an application into vertical slices, where each slice represents a complete feature or functionality. Each slice contains all the layers required to implement the feature, such as the user interface, business logic, and data access, minimizing dependencies between slices. This approach promotes modularity, maintainability, and scalability by isolating features and reducing cross-cutting concerns.
References