You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 16, 2019. It is now read-only.
Currently the provider resolves every service endpoint every x seconds. We need to find a way to optimise this by reducing the number of requests and caching.
Options include:
Attempt to proxy request, if it timeouts out or fails with 404/410, resolve the endpoint and forward on. This would act as a trigger for staleness but would directly effect atleast the first request since a endpoint change.
Try to detect and handle just differential changes
Improve use of caching
The text was updated successfully, but these errors were encountered:
Currently the provider resolves every service endpoint every x seconds. We need to find a way to optimise this by reducing the number of requests and caching.
Options include:
The text was updated successfully, but these errors were encountered: