List of software architecture styles and patterns
Template:SHORTDESC: Software Architecture Pattern refers to a reusable, proven solution to a recurring problem at the system level, addressing concerns related to the overall structure, component interactions, and quality attributes of the system. Software architecture patterns operate at a higher level of abstraction than software design patterns, solving broader system-level challenges. While these patterns typically affect system-level concerns, the distinction between architectural patterns and architectural styles can sometimes be blurry. Examples include Circuit Breaker.[1][2][3]
Software Architecture Style refers to a high-level structural organization that defines the overall system organization, specifying how components are organized, how they interact, and the constraints on those interactions. Architecture styles typically include a vocabulary of component and connector types, as well as semantic models for interpreting the system's properties. These styles represent the most coarse-grained level of system organization. Examples include Layered Architecture, Microservices, and Event-Driven Architecture.[1][2][3]
List of software architecture styles
[edit | edit source]- Event-driven architecture
- Hexagonal Architecture (also known as Ports and Adapters)
- Layered architecture
- Microkernel architecture[1]
- Pipes and Filters architecture[1]
- Microservices
- (Modular) monolithic
- Service-oriented architecture
- "Service-based architecture"[1]
- Space-based architecture
List of software architecture patterns
[edit | edit source]- Inbox and outbox pattern
- "Queue-Based Load Leveling", also known as the "Storage First Pattern", is an architectural pattern in which a queue acts as a buffer between an invoker service (such as an API Gateway) and the destination (e.g., compute resources).[4]
- "Backends for frontends" pattern[5]
- "Public versus Published Interfaces"[6]
- Asynchronous messaging
- Batch request (also known as Request Bundle pattern)
- Blackboard (design pattern)
- Circuit Breaker[1][2][3]
- Client–server model
- Competing Consumers pattern
- Model–view–controller
- Claim-Check pattern
- Peer-to-peer
- Publish–subscribe pattern
- Rate limiting
- Request–response
- Retry pattern [7]
- Rule-based
- Saga pattern
- Strangler fig pattern
- Throttling
See also
[edit | edit source]References
[edit | edit source]- ^ a b c d e f Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ a b c Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ a b c Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).