Markdown
Distributed System Architectures - Markdown
Distributed system architectures are architectural patterns for designing and building systems where multiple independent computers or services work together. Various patterns exist, including microservices, event-driven architecture, and service-oriented architecture (SOA), each with different characteristics and applicable scenarios. These architectures are widely used to achieve scalability, fault tolerance, and flexibility.
distributed systems
microservices
event-driven
SOA
system design
architecture patterns
| code | slug | name | description | category |
| --- | --- | --- | --- | --- |
| 01 | microservices-architecture | Microservices Architecture | An architecture that builds applications as a collection of small, independent services. | Service Decomposition Pattern |
| 02 | event-driven-architecture | Event-Driven Architecture | An architecture that designs systems around the production, detection, consumption, and reaction to events. | Communication Pattern |
| 03 | service-oriented-architecture | Service-Oriented Architecture | An architecture that builds applications as a collection of loosely coupled, reusable services. | Enterprise Pattern |
| 04 | api-gateway-pattern | API Gateway Pattern | A pattern that provides a single entry point between clients and backend services. | Communication Pattern |
| 05 | cqrs-pattern | CQRS Pattern | A pattern that separates read operations from write operations into different models. | Data Pattern |
| 06 | saga-pattern | Saga Pattern | A pattern that manages distributed transactions by breaking them into multiple local transactions. | Transaction Pattern |
| 07 | outbox-pattern | Outbox Pattern | A pattern that guarantees consistency between database transactions and event publishing. | Data Pattern |
| 08 | sidecar-pattern | Sidecar Pattern | A pattern that deploys a helper component alongside the main application. | Deployment Pattern |
| 09 | strangler-fig-pattern | Strangler Fig Pattern | A migration pattern for gradually replacing legacy systems with new systems. | Migration Pattern |
| 10 | circuit-breaker-pattern | Circuit Breaker Pattern | A pattern that performs failure detection and automatic recovery to prevent cascading failures. | Fault Tolerance Pattern |
| 11 | sharding-pattern | Sharding Pattern | A pattern that distributes data horizontally across multiple databases. | Data Pattern |
| 12 | event-sourcing-pattern | Event Sourcing Pattern | A pattern that stores application state as a sequence of events. | Data Pattern |