Throttling is a typical feature of any platform with API management capabilities. The API Hub implements throttling of requests by TPPs, based on the counters described in the table below. TPP by Client by LFI, by API operation: A given Client identified by Client ID or certificate thumbprint accessing a given LFI. TPP by TPP ID by LFI: A given TPP identified by TPP ID accessing a given LFI. All Clients associated with the TPP will be throttled on a given LFI instanceThis can be throttled at for a given API operation, providing traffic shaping focused on specific API calls. TPP by Client by API Hub: A given Client identified by Client ID or certificate thumbprint accessing more than one LFI instance on the API Hub. The Client will be throttled across all LFI instances at the API Hub. TPP by TPP ID by API Hub: A given TPP identified by TPP ID accessing more than one LFI instance on the API Hub. The TPP will be throttled across all LFI instances at the API Hub. Platform: System-wide backstop, designed to throttle all TPPs based on all load on the API Hub.
The throttling described here is expected to be appropriate for protecting LFIs at their Ozone Connect APIs. LFIs should, however, Throttling will be configured on the API Hub as per the requirements of the CBUAE using the parameters described above. LFIs should implement traffic shaping and throttling at their Ozone Connect APIs that is appropriate to the capabilities of their platform and to protect the stability of their systems. Throttling will be discussed in more detail during onboarding. | 