Tag
Five layers walked top to bottom — browser headers, CDN edge with its famous incident, Redis with a job description, database-adjacent options — plus the staleness grid that makes TTLs a product decision.
Why revocation is where stateless goes to die, the XSS blast-radius problem, the specific habitats where JWTs genuinely shine, and the sessions-at-the-edge / tokens-between-machines architecture.
The unanswerable-timeout thought experiment, the implementation with its three traps disarmed, why the property must compose down the whole call chain, and the cheaper natural-key alternatives.
The specific problem it solves brilliantly, the five bills itemized — resolver N+1s, forfeited HTTP caching, query-surface DoS, field-level auth, the toolchain — and the BFF alternative most teams actually need.
What gRPC actually is (three technologies in a trench coat), the honest performance paragraph, where each protocol is simply correct, and the hybrid edge-REST/interior-gRPC topology mature systems converge on.
From both sides of hundreds of integrations: honest status codes, RFC 7807 errors with trace IDs, cursor pagination, idempotency and versioning posture, and the DX multipliers that halve support tickets.
A smart queue versus a replicated log: routing, per-message semantics and DLX on one side; replay, independent readers and partition ordering on the other — plus the framework-queue option the rivalry hides.
Payloads as IDs and intent, the 0-1-3 execution assumption, retry policies you design instead of inherit, lanes by latency class, and the four dashboard numbers that catch every queue pathology.
The lost update, the phantom check, the inconsistent report, the cross-row invariant — each real bug matched to its cheapest cure, from atomic updates to Serializable retry loops, plus deadlock etiquette.
Intent vs delivery as the founding seam: a typed notification catalog, a preference engine that resolves instead of looks up, queue-per-channel adapters, digesting, and the build order that avoids the rewrite.
