I am a bit curious how exactly it is stored at least with a postgres back end. like does it fall apart if I start having 10 million rules in total? or maybe 1 million rules per tenant?
I can just look at it and figure it out though
I could use this pattern to load the model, but I'm starting to think that it might have performance implications if I am targeting a budget of one millisecond for each request. https://casbin.org/docs/model-storage/#load-model-from-code
I want to use casbin for several projects, and all of them have the same pattern where each tenant (think company or discord server) in the app has its own admin definable permissions policy. I noticed that in the docs for model storage it says this:
Casbin models are designed to be loaded rather than saved. The model defines your access control logic and should remain static at runtime, so Casbin does not provide an API for persisting model changes to storage.
For my use case, the models are updated infrequently, but should not require an application restart. what would be the best way to approach this kind of use case?
its something like for the vast vast majority of the time, the policy won't change

