Tag
Three signals and the different questions they answer, the trace-ID join that delivers 80% of the value, the collector pattern, tail-based sampling that keeps the interesting 100%, and the incident-driven rollout.
The four flag species and why conflating them causes misery, sticky percentage rollouts with one decision point, the staged rollout playbook with observability hooks, and the hygiene that prevents flag archaeology.
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.
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.
Where Postgres genuinely pulls ahead, where MySQL holds real ground, the differences everyone overweights, and a decision procedure whose top factor is organizational, not technical.
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.
Permission as a spendable one-shot resource, the token registry your backend must own, deep links as versioned contracts, sending discipline with collapse keys and quiet hours, and the four health metrics.
Sockets are tenants, not confetti: the pub/sub backplane, stateless nodes and rolling drains, the reconnect stampede and its jittered cure, missed-message recovery by data shape, and the capacity cliffs to test first.
The honest tour by operational weight: Postgres tsvector with trigrams, the search-box specialists with superb typo tolerance, and the real signals that justify the heavyweight cluster.
The ladder from additive changes to real versions: tolerance rules that make 90% of changes free, deprecated-field telemetry, Sunset headers, brown-outs, and the internal-API discount.
