Loading
Topic
Architecture decisions for system framing, service boundaries, communication, consistency, replication, partitioning, and distributed workflows.
Practice items tagged with Distributed System Foundations.
Maps business invariants and stale-data tolerance to strong or eventual consistency, explicit failure behavior, reconciliation, and user-visible state.
Designs a multi-service business workflow using local transactions, durable progress, idempotency, retries, and domain-specific compensation.
Designs a sharding strategy with a stable key, balanced load, routing, resharding, cross-shard limits, and operational ownership.
Chooses safe cached, partial, pending, read-only, or unavailable behavior and makes degraded state explicit to clients and operators.
Uses read replicas selectively while accounting for stale reads, read-after-write behavior, routing, failover, query cost, and replication health.
Frames a vague system-design problem with explicit flows, constraints, scale estimates, and measurable quality targets before selecting components.