Topic
10 posts tagged “Distributed Systems”.
Chisato · · 4 min read Event sourcing stores every state change as an immutable event instead of overwriting current state. How it works, and when CQRS pairs with it.
Chisato · · 5 min read Exponential backoff spaces retries further apart after each failure so clients stop hammering a struggling service. How it works, and why it needs jitter.
Chisato · · 5 min read CQRS separates the code paths that change data from the code paths that read it. How it works, why teams adopt it, and when it's overkill.
The Lycoris Team · · 5 min read Raft is a consensus algorithm that lets a cluster of servers agree on a shared state even when some nodes fail. How leader election and log replication work.
Chisato · · 4 min read Active-active runs every region live and load-balanced; active-passive keeps a standby idle until failover. How each affects cost, consistency, and recovery.
Chisato · · 5 min read Publish-subscribe decouples senders from receivers through a message broker, letting services communicate without knowing who's listening.
The Lycoris Team · · 4 min read The saga pattern coordinates a multi-step transaction across services using local commits and compensating actions instead of a distributed lock.
The Lycoris Team · · 5 min read Two-phase commit coordinates a transaction across multiple databases with a prepare phase and a commit phase, trading availability for strong consistency.
Chisato · · 4 min read Eventual consistency guarantees that replicas converge over time, not instantly. How it differs from strong consistency and when it's acceptable.
Chisato · · 4 min read CAP theorem says a distributed system can't guarantee consistency, availability, and partition tolerance all at once. What the trade-off means in practice.
