Performance

The web service is designed to handle a maximum of 200 authorization requests per minute, with at least 95% of the requests resulting in authorised=true.

Policy for Service Users: Load Reduction via Caching

It is possible that service users may be queried with high frequency during the processing of large orders. If each of these service calls were repeatedly authorized by sedex, the sedex system would experience a significant load.

Such tight performance coupling is often unnecessary, as the results of authorization requests can be temporarily stored in an authorization cache on the service provider's side and answered locally for a certain period (e.g., for one hour).

User Group

The primary goal of sedex is secure and reliable message transport. This core function should not be jeopardized by overloading the secondary product, the participant directory, and authorization for other purposes.