We are evaluating if we can use Kong as a forward api proxy. I do understand that Kong has a forward api proxy plugin in the enterprise edition but I would like to get more details for the below requirements.
We are integrating external systems through REST api’s which are slow in performance. We would like to understand if Kong can act as a forward api proxy to cache the api responses from the external systems.
- How does Kong forward proxy handle API rate limiting errors from external systems? We have around 6000 api resources being called by our application deployments. Can Kong pause the ongoing the api calls once any one of them receives an HTTP 429 error?
- How does Kong forward proxy retry api calls on failures? Does it have a backoff policy?
- Can Kong be configured such that it prioritizes certain api calls over others?
Kindly let me know your thoughts.
Thanks!