Agave API acts as a proxy to the Source Systems' APIs.
In practice, this means the following:
- The response time for an API request will vary depending on the response time of the Source System APIs are slow or down for maintenance, the corresponding Agave API request will also be slow or unresponsive.
- Agave API will add some latency to a request (e.g. 5-10ms per request).
In most cases, Agave API will retry a request that either timed out of failed with a server error. However, certain Source Systems provide very restrictive Rate Limits which make retrying failed requests more difficult.
If you are building an integration with the Agave API, you should take the variable response times into account. For example, you might want to build loading indicators in your front-end.