Edge Rendering
Running the render close to the user, and the personalisation and cache trade it implies.
5 to work through
-
advanced
A frontend platform runs functions at the edge for personalisation but must read user data that lives in one region. Which computations genuinely belong at the edge, and when does "edge" make debugging and consistency worse?
3 min answer -
advanced
A platform can render at the edge, close to the user. Which workloads benefit, and which become harder?
2 min answer -
advanced
Design personalised page delivery at the edge for a global site. What can move to the edge, and what must not?
1 min answer -
advanced
Marketing wants personalised content on pages currently cached at the edge with a 24-hour TTL. How do you preserve performance?
2 min answer -
advanced
Marketing wants personalised content on pages currently cached at the edge with a 24-hour TTL. Preserve the performance.
2 min answer
3 terms in this topic
Data Proximity
The observation that moving compute toward the user moves it away from the data, so edge execution helps only for computations that do not need a cen…
patternEdge Personalisation
Varying a cached response at the edge on a small number of attributes, so the page stays cacheable while still differing per visitor segment.
patternEdge Rendering
Producing a page's HTML in a lightweight runtime at a CDN point of presence rather than in a regional data centre - which removes network distance fr…
Neighbouring topics
Frontend & Experience Architecture
General material on architecting the surface the user actually touches.
Rendering Strategies
Client, server, static and incremental rendering, and what each costs on first paint.
Hydration Cost
The gap between visible and interactive, and the JavaScript that closes it.
Micro-Frontends
Independent deployment of UI slices, and the shared runtime that undermines it.
Module Federation
Loading code from another build at runtime, with versioning and failure to think about.
UI Monorepo Strategy
One repository for many front ends, and the build graph that makes it viable.
Design Systems
Components as a versioned internal product, with adoption and deprecation like any API.
Component Contracts
Props, slots and events as an interface, and the breaking change hidden in a style.
Client State Architecture
Server state, UI state and derived state, and why conflating them causes most bugs.
Client Caching & Data Layer
Stale-while-revalidate, invalidation and optimistic updates on the client.
BFF for Experience
One backend per experience, shaped by the screen rather than by the domain.
API Shapes for UI
REST, GraphQL and RPC judged by over-fetching, round trips and client coupling.
Web Performance Budgets
A number a build can fail against, rather than a performance sprint once a year.
Core Web Vitals
LCP, INP and CLS — what they measure, and the architecture that moves them.
Accessibility Architecture
Semantics, focus management and announcements designed in rather than audited in.
Internationalisation
Locale, direction, pluralisation and dates as structural concerns, not string tables.
Client Feature Flags
Flag evaluation on a device you do not control, and the flicker and staleness it brings.
Real User Monitoring
Field data from real devices and networks, against the synthetic run that looked fine.
Frontend Security
CSP, XSS, CSRF, token storage, and the trust boundary that ends at the browser.