Skip to main content

22 docs tagged with "Tier 2 — Distributed thinking"

What changes once a call can cross a network and fail halfway.

View all tags

API Resource Modeling

Rule: an API manages the lifecycle of resources; it does not expose your actions or your tables.

Availability Patterns

Availability is arithmetic before it is architecture. The arithmetic is worth doing first, because

CAP Theorem

CAP is the most cited and most misquoted result in distributed systems. The popular version —

Consistency Models

A consistency model is a contract about what a read is allowed to return. It is not a quality

Designing for Failure

Rule: failure is the default state, not the exception. Large systems are not designed for the

Latency Numbers

The point of knowing these is not recall for its own sake. It is being able to reject a design in

Raft

* Network messages can be delayed, reordered, or lost.

Rate Limiting

Rule: without a limit, one client's mistake becomes everyone's outage. A rate limit is not

Replication & Sharding

Rule: a replica is a different point in time, and a shard key is a decision you cannot undo.

The Network & Latency

Rule: a healthy service plus a healthy service does not equal a healthy system. The network

Timeouts & Retries

Rule: retry without idempotency is not error handling — it is a bug. And a retry that fires

Webhook Provider Design

Rule: sending a webhook once is not delivering it. Without signatures, retries, and a way to