They differ in how long a result lives and who shares it.
React's cache(fn) is request-scoped memoization, a React API for Server Components. Within one server render, calls with the same arguments (compared with Object.is, so objects by reference) return the same result; React drops it all when the request ends. Its job is deduplication: three components calling getUser(id) cause one query. It stores live values, not serialized ones.
use cache (Next.js, with cacheComponents: true) is a persistent cache. The result is serialized and stored in a cache handler, by default in-process memory, and reused by later requests and other routes until its cacheLife runs out or a cacheTag is invalidated. The key is computed for you: build ID, function identity, serialized arguments and closed-over values. It also decides what goes into the prerendered static shell. Entries don't survive a new build.
unstable_cache(fn, keyParts, { tags, revalidate }) is the older Next.js cross-request cache. Its key is your keyParts plus the arguments and the function's source text, so a closed-over variable must be added to keyParts by hand. It is stored in Next's data cache (on disk under next start) and, per the docs, persists across deployments, which use cache does not. It still works with Cache Components; the migration guide maps revalidate to cacheLife and tags to cacheTag.
The pieces combine rather than compete: use cache for what can be reused across users, React's cache for per-request dedup of uncached or request-specific reads, unstable_cache only when data must outlive a deploy.
Legacy: in Next.js 15, Cache Components was experimental (experimental.dynamicIO, later experimental.cacheComponents); 16.0 made cacheComponents a top-level option.