You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Pollendina service uses an in memory database (golang map) to store token=>CN authorizations. In order to support horizontal scaling of the Pollendina service and durability, some persistent or distributed database should be adopted.
A backend plugin infrastructure would be nice. That way adopters could use Consul, etcd, Redis, etc.
Alternatively, clustering could be embedded into the service for service-to-service memory sharing. One reason this may be preferred is that this is access control data. Securing the storage of the authorization content is at least as important as providing the authorization mechanism in the first place.
The text was updated successfully, but these errors were encountered:
Currently the Pollendina service uses an in memory database (golang map) to store token=>CN authorizations. In order to support horizontal scaling of the Pollendina service and durability, some persistent or distributed database should be adopted.
A backend plugin infrastructure would be nice. That way adopters could use Consul, etcd, Redis, etc.
Alternatively, clustering could be embedded into the service for service-to-service memory sharing. One reason this may be preferred is that this is access control data. Securing the storage of the authorization content is at least as important as providing the authorization mechanism in the first place.
The text was updated successfully, but these errors were encountered: