Networking, caching & HTTP for UIs
Core details
| Concern | Key ideas |
|---|---|
| Critical path | LCP hero discovery: priority hints, preload only with measurable proof |
| Versioning | content-hashed filenames → long immutable cache safely |
| HTML policy | rarely long immutable—stale UX + personalization traps |
Cache-Control | max-age, s-maxage, stale-while-revalidate semantics verbally precise |
ETag / 304 | bandwidth win + correctness when validators align |
| Prefetch/prerender | speculate only with UX intent—not blanket autopilot firing |
Discuss CDN surrogate key purging narratives when dynamic HTML edge cached dangerously—mention ban paths explicitly.
Understanding
Most win comes from changing what ships and in what order, not from squeezing bits. Hash-versioned static assets can safely live at long TTLs; HTML and personalized responses almost never should without strict keying and purge discipline. GET APIs cached for “speed” can lie to the UI about business truth—pair caches with explicit freshness contracts and user-visible cues when data may be stale.
Senior understanding
| Probe angle | Credibility artifact |
|---|---|
| “Prove regression” | Network waterfall screenshot before/after with identical throttle profile |
| “Who owns keys?” | cross-team SLA on purge events / surrogate invalidation choreography |
| “Security posture” | zero mixed-content; strict transport headers alignment awareness |
Third-party weight: escalate marketing injectables through risk review—SLO-aware loading, deferred consent-aware activation, kill switches—not “marketing exception” culture.
Diagram
See also
Last updated on
Spotted something unclear or wrong on this page?