Casbin-server and caching

[FlyveHest]

I am looking into using Casbin in a project, but I am a bit concerned about performance, and I can't really find any good info about how casbin-server works internally.

What I am hoping is that upon start the server loads the policy from storage (which will most likely be a SQL backend), and then keeps it in memory until server is shut down or restarted.

I'm guessing that all changes to the policy should then be performed via the API, which then auto-saves to the backend and updates internal states on changes.

Can anyone confirm that this is how the server operates? Loading and parsing the entire policy on each request does not seem very performant to me, if the project is going to be serving a couple of requests per second, and policy is comprehensive (some hundred users and likely a resource count in the thousands)

[hsluoyz]

@FlyveHest I recommend looking at the newer Casbin centralized auth platform, Casdoor: https://casdoor.org/ . New features will be added there

Docs: https://casdoor.org/docs/permission/overview

Code: https://github.com/casdoor/casdoor

[FlyveHest]

@hsluoyz Thanks for the reply, but it doesn't really answer my question.

I already looked at Casdoor, but I am not looking for a complete pacakage including authentication, I was looking at Casbin to have authorization separated from authentication.

It looks like casbin-server is being actively updated, but maybe it isn't a good match for an authorization only service?

[hsluoyz]

IFAIK, no many open source efforts are focusing on Casbin-Server. You either look at Casdoor open source, or Casbin Enterprise services (pay for people to get what you want).