FrontendHaltNetworking·Advanced·Conceptual·1 min read
Where should data requirements live to avoid waterfalls in a routed app?
Short interview answer
Hoisted to the route or a loader that runs before the component tree renders, so all of a route's data requests can start together. Fetching inside deeply nested components that only mount after their parents resolve is the structural cause of waterfalls.
Key takeaway
Explain the underlying mental model clearly, then support it with a concrete example and its trade-offs.