skip to content

Data Loading & Caching

4 roadmaps32 questions

Where a route reads and writes data, which copies of the result are kept and who may see each, and what a write invalidates. Interviewers probe it because stale or leaked data is the classic bug here.

on this pageshow

explore

questions

page 2 of 2

As a lead, how would you decide what data a route must declare up front versus what deeper parts of the page may request themselves?

level: principalimportance: nice to knowfreq 38%

basics

~20 s

Make route-declared the default for whatever the first view needs: it lets reads overlap and keeps a URL's cost legible. Allow documented exceptions for secondary, interaction-driven and highly personalised data, and enforce it with a per-route budget.

open as a page

Your team wants every core write to work before any script loads; how do you decide which writes get that guarantee?

level: principalimportance: nice to knowfreq 34%

basics

~20 s

Grade writes by what a failure in the pre-hydration window costs, not by how many users disable scripting. Guarantee the small number on the revenue and account path, accept the scripted-only path elsewhere, and test the guarantee or it decays.

open as a page

showing 31–32 of 32