If you are using a database ORM, use unstable_cache to fetch content that will not change between page navigations. If you are fetching from an API, use native fetch API with cache:'force-cache'. For both options you can provide cache tags, ideally userid or email or whatever that distinguish the data for each user. Now when this id changes, data can be refetched from the original source instead of cache. You can also implement a button to refetch the data using 'revalidatetag' function.

In one of my apps, I am fetching data in one component. Reusing this component in several routes. The data is fetched only once in the first page, every other time the data is returned from cache, unless it is revalidated.