[Question] How to handle large peristent stores?

[skoenfaelt]

Hello,
we are integrating a selfmade permission management system.
Basically we have a user which has groups and roles and via those we fetch all his permissions.
Lets say the app is grown and we have many permissions > 1000.

Perisisting all the permissions of a user (lets say 60), then we have the issue with the cookie size. A cookie with 60 guids is larger than 4kb (max cookie size)

One workaround might be putting this store into the localstorage. This is not best practice due its lack of security and its not SSR friendly.
Another workaround might be partition a cookie. This is not a web standard as far as I know.

How do you handle persisting larger stores? Do you have better Ideas?
This might lead into improvements of the pinia peristenstate docs.

[skoenfaelt]

I have made some thoughts.
Our approach is not that legal in terms of the eu gdpr.
So the correct way would be store data in the pinia store and only persist (if needed) those app data like theme settings...

So the userStore should not persisted. I do not like that approach, since you need to lead the needed data on f5 instead of consuming the store. That will lead to more traffic.
The permissions could stored in the session/ localstorage (maybe with node crypto "secured")

What are your ideas on that topic? Still, how do you handle large persisted stores?