Architecture Patterns
An architectural pattern is a reusable, concrete solution to a recurring design problem, often applicable to the internal organization of modules or services. While a style is a blueprint for the entire house, a pattern is a blueprint for a specific room or system inside that house, like the plumbing. Typical examples include Hexagonal Architecture, which organizes business logic by isolating it from external dependencies, the Model-View-Controller (MVC) pattern, which organizes user interface logic, or the Event Sourcing pattern, which manages data persistence. The commonality with styles, as explained on the “Architectural Styles” page, is that both provide proven solutions to design problems. The key difference lies in their scope: patterns define an organization at the scale of a subsystem or module, without dictating the global structure of the entire system, while styles define the organization of the entire ecosystem.
Application Architecture Patterns
- Blackboard Pattern
- Broker
- Clean Architecture
- CQRS (Command Query Responsibility Segregation)
- Event Sourcing
- Hexagonal Architecture
- Modern Application Architectures
- Modular Monolith
- Microfrontends
- Model-View-Controller (MVC)
- Model-View-Presenter (MVP)
- Model-View-ViewModel (MVVM)
- Model-View-Whatever (MVW)
- Onion Architecture
- Pipe and Filters Pattern
- Saga
- Service Mesh
- Strangler Fig
- API Gateway
- Backends for Frontend (BFF)