Streaming with Suspense boundaries

Do not let the slowest query set the pace

Without streaming, the response waits for every await on the page. One slow recommendation service and the entire document is held back, including the header the user could have seen instantly.

A Suspense boundary breaks that coupling. Everything outside it is flushed to the browser immediately with the fallback in place, and the real content is streamed in when it resolves.

A loading file is exactly this: an implicit Suspense boundary around the route segment. Nesting boundaries more tightly gives you finer control over what appears when.

Streaming does not make your data faster. It stops one slow query from holding the whole page hostage.