distributed-systems-patterns

Installation
SKILL.md

Distributed Systems Patterns

Read-only pattern lens. Two bodies of knowledge: the topology route follows Burns, Designing Distributed Systems (name the container-shaped pattern, then reuse or compose it); the event-driven route follows Bellemare (a durable, replayable data communication layer of schematized streams, not messages that vanish after consume). Don't invent a one-off topology the catalog already names, and don't call a delete-after-consume queue an event architecture.

The four failures this lens stops: reinventing a named primitive; a multi-node pattern where a coscheduled pair would do, or an election where a singleton would do; event-driven microservices where a modular monolith is cheaper; and building them without a data communication layer (implicit schemas, shared databases, CDC as the destination).

Elsewhere: overall style and service decomposition → architecture-lens; outbox writes, idempotency, retries, dead-letter handling, and transactions in code → data-systems-coding-lens; bounded-context alignment → domain-driven-design; in-process object structure → software-design-philosophy; agent loops → agent-architecture-lens.

Select the route

Need Read
Containers, replicas, shards, scatter/gather, FaaS, election, work queues, batch pipelines references/topology.md
Adopt, review, or migrate event-driven services and public streams references/event-driven.md

Choose the smallest pattern that meets the constraint. If no distributed pattern fires, say so and stop.

Leitwörter

Installs
47
GitHub Stars
2
First Seen
Aug 19, 2026