HTML

Distributed System Architectures - HTML

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

<table>
<thead><tr><th>code</th><th>slug</th><th>name</th><th>description</th><th>category</th></tr></thead>
<tbody><tr><td>01</td><td>microservices-architecture</td><td>Microservices Architecture</td><td>An architecture that builds applications as a collection of small, independent services.</td><td>Service Decomposition Pattern</td></tr>
<tr><td>02</td><td>event-driven-architecture</td><td>Event-Driven Architecture</td><td>An architecture that designs systems around the production, detection, consumption, and reaction to events.</td><td>Communication Pattern</td></tr>
<tr><td>03</td><td>service-oriented-architecture</td><td>Service-Oriented Architecture</td><td>An architecture that builds applications as a collection of loosely coupled, reusable services.</td><td>Enterprise Pattern</td></tr>
<tr><td>04</td><td>api-gateway-pattern</td><td>API Gateway Pattern</td><td>A pattern that provides a single entry point between clients and backend services.</td><td>Communication Pattern</td></tr>
<tr><td>05</td><td>cqrs-pattern</td><td>CQRS Pattern</td><td>A pattern that separates read operations from write operations into different models.</td><td>Data Pattern</td></tr>
<tr><td>06</td><td>saga-pattern</td><td>Saga Pattern</td><td>A pattern that manages distributed transactions by breaking them into multiple local transactions.</td><td>Transaction Pattern</td></tr>
<tr><td>07</td><td>outbox-pattern</td><td>Outbox Pattern</td><td>A pattern that guarantees consistency between database transactions and event publishing.</td><td>Data Pattern</td></tr>
<tr><td>08</td><td>sidecar-pattern</td><td>Sidecar Pattern</td><td>A pattern that deploys a helper component alongside the main application.</td><td>Deployment Pattern</td></tr>
<tr><td>09</td><td>strangler-fig-pattern</td><td>Strangler Fig Pattern</td><td>A migration pattern for gradually replacing legacy systems with new systems.</td><td>Migration Pattern</td></tr>
<tr><td>10</td><td>circuit-breaker-pattern</td><td>Circuit Breaker Pattern</td><td>A pattern that performs failure detection and automatic recovery to prevent cascading failures.</td><td>Fault Tolerance Pattern</td></tr>
<tr><td>11</td><td>sharding-pattern</td><td>Sharding Pattern</td><td>A pattern that distributes data horizontally across multiple databases.</td><td>Data Pattern</td></tr>
<tr><td>12</td><td>event-sourcing-pattern</td><td>Event Sourcing Pattern</td><td>A pattern that stores application state as a sequence of events.</td><td>Data Pattern</td></tr></tbody>
</table>