!Warning: Impact on User-Specific Caching in a SaaS Model

[ChoaibMouhrach]

Goals

1. Cache data per user

Non-Goals

1. Global cache

Background

Hello,

I have a question after going through the documentation. I'm using a SaaS model and have a function like this:

export const getAuthUserAction = unstable_cache(
  async () => {
    const session = await getAuthUser();

    if (!session?.user.id) {
      return session;
    }

    const user = await db.query.users.findFirst({
      where: eq(users.id, session.user.id),
    });

    if (!user) {
      return session;
    }

    session.user.email = user.email;
    session.user.image = user.image;
    session.user.name = user.name;

    return session;
  },
  ["auth"],
  {
    tags: ["auth"],
  }
);

I also have other actions with revalidateTag("auth"). Does this mean that when a user revalidates the cache, it affects the cache for all users?

If yes,

Is there a way to create unique cache keys for each user?

If no,

Doesn't this suggest that the caching system is not very useful for this type of application?

Proposal

Add the ability to add a user ID in the cache key