Redis seems to be only used for authorization within the backend. Is that correct?
If so, authorization can be moved into the frontend itself (via the OAuth2.0 PKCE flow). Keycloak itself can be configured in a way such that any token issued for the lagertool_frontend client can be used by the lagertool_backend client (to which you can assign roles such as admin or editor). Do you see an issue with that? The frontend still does not require anything other than static files hosted.
redis has its use cases, but I think if it is only used for this, an effort can be made to remodel this.
Redis seems to be only used for authorization within the backend. Is that correct?
If so, authorization can be moved into the frontend itself (via the OAuth2.0 PKCE flow). Keycloak itself can be configured in a way such that any token issued for the
lagertool_frontendclient can be used by thelagertool_backendclient (to which you can assign roles such as admin or editor). Do you see an issue with that? The frontend still does not require anything other than static files hosted.redis has its use cases, but I think if it is only used for this, an effort can be made to remodel this.