25 editable reference diagrams
Distributed Systems Architecture Diagrams
Distributed systems trade local simplicity for independent execution across network and failure boundaries. These diagrams cover coordination, messaging, consistency, retries and the patterns that keep partially completed work understandable.
Begin with the failure you must tolerate. Trace what happens after a timeout, repeated request or lost acknowledgement. Compare an outbox, saga, idempotency store or durable workflow by the guarantees each actually supplies, rather than treating them as interchangeable boxes.
Choose a diagram for your design question
Open a reference to inspect its component flow and trade-offs, then adapt it in the browser-local editor. Manual editing does not require login; AI generation and account storage do.

Distributed system architecture
Treat network calls as independent failure boundaries.
7 components · 7 connections
Explore distributed system architecture →
CQRS architecture diagram
Accept explicit projection lag between writes and reads.
6 components · 6 connections
Explore cqrs architecture diagram →
Event sourcing architecture
Events are authoritative history rather than mutable rows.
6 components · 6 connections
Explore event sourcing architecture →
Saga orchestration architecture
Record each step and its compensating action.
6 components · 6 connections
Explore saga orchestration architecture →
Saga choreography architecture
Avoid central orchestration while preserving event contracts.
6 components · 6 connections
Explore saga choreography architecture →
Transactional outbox architecture
Commit business state and publication intent together.
7 components · 6 connections
Explore transactional outbox architecture →
Backend for frontend architecture
Tailor aggregation without duplicating business ownership.
6 components · 6 connections
Explore backend for frontend architecture →
API composition architecture
Budget latency and partial failures across dependencies.
6 components · 6 connections
Explore api composition architecture →
Strangler fig migration architecture
Move routes incrementally while controlling dual ownership.
7 components · 7 connections
Explore strangler fig migration architecture →
Anti corruption layer architecture
Prevent legacy terminology from leaking into new policy.
5 components · 4 connections
Explore anti corruption layer architecture →
Distributed transaction architecture
Identify blocking and recovery behavior before coordination.
7 components · 7 connections
Explore distributed transaction architecture →
Distributed locking architecture
Use fencing to reject work from expired holders.
6 components · 5 connections
Explore distributed locking architecture →
Distributed task scheduler architecture
Persist task identity before dispatch and retry.
6 components · 5 connections
Explore distributed task scheduler architecture →
Distributed job queue architecture
Acknowledge after durable processing and deduplicate side effects.
6 components · 6 connections
Explore distributed job queue architecture →
Distributed rate limiter architecture
Choose explicit fail-open or fail-closed behavior.
5 components · 5 connections
Explore distributed rate limiter architecture →
Consistent hashing architecture
Plan key movement and replication during membership changes.
6 components · 5 connections
Explore consistent hashing architecture →
Leader election architecture
A lease alone does not prevent stale leader writes.
6 components · 5 connections
Explore leader election architecture →
Distributed consensus architecture
Only acknowledge decisions after the required quorum.
6 components · 6 connections
Explore distributed consensus architecture →
Service discovery architecture
Control stale endpoints and registry outage behavior.
6 components · 5 connections
Explore service discovery architecture →
Circuit breaker architecture
Use bounded probes rather than synchronized retry storms.
6 components · 5 connections
Explore circuit breaker architecture →
Bulkhead isolation architecture
Reserve capacity so one dependency cannot exhaust all work.
7 components · 7 connections
Explore bulkhead isolation architecture →
Idempotent API architecture
Bind operation keys to payload identity and retention.
6 components · 6 connections
Explore idempotent api architecture →
Distributed cache architecture
Define ownership and invalidation before adding cache replicas.
6 components · 5 connections
Explore distributed cache architecture →
Workflow orchestration architecture
Durable workflow state is separate from external side effects.
6 components · 6 connections
Explore workflow orchestration architecture →
Durable execution architecture
Replay deterministic decisions and isolate nondeterministic effects.
7 components · 8 connections
Explore durable execution architecture →