Delivering Baseline Experiences and Refreshing Server Components

Ryan and Sam talk about how to invalidate Next.js’ client-side cache when a different session makes changes to backend data, and ultimately discuss whether clicking a link to a URL vs. hitting refresh on that same URL should render the same page if no backend data has changed.

Topics include:

• 0:00 - Intro
• 1:00 - Suspense boundary identity and the Await component
• 11:07 - How to refresh RSC using a Server Action
• 27:17 - The difference between a navigation and a page refresh

Links:

• Ryan’s Data Fetching with RSC course
• Refresh App Router code recipe