Artwork

Content provided by Frontend First, Sam Selikoff, and Ryan Toronto. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Frontend First, Sam Selikoff, and Ryan Toronto or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

React Deep Dive: cache

1:07:28
 
Share
 

Manage episode 399728785 series 1635850
Content provided by Frontend First, Sam Selikoff, and Ryan Toronto. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Frontend First, Sam Selikoff, and Ryan Toronto or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Ryan and Sam discuss the purpose and usage of the cache() function, a new experimental API from React.

Topics include:

  • 0:00 - Intro
  • 2:29 - Caching in Next.js vs. React cache()
  • 8:11 - Why React invalidates the cache for each server request
  • 14:43 - How cache() enables colocation of data-fetching code
  • 16:14 - Using cache() to share CPU-heavy or I/O-bound tasks between components
  • 19:31 - Why cache() obviates the need for context in Server Components
  • 23:19 - The danger of module scope on the server
  • 27:54 - Why cache() is implemented with AsyncLocalStorage
  • 41:04 - Why cache() is part of React
  • 48:27 - Why Server Components don’t support cache()
  • 53:04 - How cache() eliminates waterfalls

Links:

  continue reading

191 episodes

Artwork

React Deep Dive: cache

Frontend First

209 subscribers

published

iconShare
 
Manage episode 399728785 series 1635850
Content provided by Frontend First, Sam Selikoff, and Ryan Toronto. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Frontend First, Sam Selikoff, and Ryan Toronto or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Ryan and Sam discuss the purpose and usage of the cache() function, a new experimental API from React.

Topics include:

  • 0:00 - Intro
  • 2:29 - Caching in Next.js vs. React cache()
  • 8:11 - Why React invalidates the cache for each server request
  • 14:43 - How cache() enables colocation of data-fetching code
  • 16:14 - Using cache() to share CPU-heavy or I/O-bound tasks between components
  • 19:31 - Why cache() obviates the need for context in Server Components
  • 23:19 - The danger of module scope on the server
  • 27:54 - Why cache() is implemented with AsyncLocalStorage
  • 41:04 - Why cache() is part of React
  • 48:27 - Why Server Components don’t support cache()
  • 53:04 - How cache() eliminates waterfalls

Links:

  continue reading

191 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide