The current authorization check is constant in the size of the authorization table (adding many authoriozations will not make it slow) but it scales linearly with the size of the resource instance table for which authoriation checks are performed. Example: increasing the size of the task table will add a constant overhead for each task.
For history this can be solved with
For runtime entites, a more efficient approach can be implemented. Property that we aim for:
log scale for a growing number of resource instances
- implement more efficient auth check
- the efficient auth check is used when there are no revoke auth in the DB
- when the user creates the first REVOKE auth in ADMIN, a warning is shown
- documentation explains this