[IDM.TSA.E1.00015] Storage Implementation
The storage layer for policy storage MUST be implemented in a way that no specific database
technology is strictly required for the purpose of policy execution. The implementation MUST
support the following levels:
1) Policy Service uses internal storage for cloning the policy repositories. This level supports
not just in time sync, but a very quick usage of simple, not often changed policies. Policy
change requires container restart. This can be realized by a script during container
startup (if configured)
2) The policy service uses an external storage to pick up the policies. E.g., from a postgres
db, a mongodb or similar. The external storage provides events when a policy has
changed, or a sync happens
Both levels MUST be configurable and adaptable by an internal interface e.g., IPolicyStorage to
allow additional implementations in the future for internal and external storage
implementations.