|
Hi Craig McNally,
I think we need to work out the details as to when edge service should return 503, specifically what would be an indicator that the service is overloaded. A couple of options to begin the discussion are:
1. When the request to mod-oai-pmh times out
Currently we return 408 status code in this case, but may return 503 with an assumption (because we don't really know why) that time-out happened due to high load
2. Make use of circuit-breaker to calculate number of unexpected errors returned by mod-oai-pmh and return 503 once certain threshold is reached
This is questionable option, because unexpected errors are not an indicator that service is overloaded
Let's discuss it on the grooming meeting.
|
|
After discussing with Hkaplanian we decided to scrap this.
- If the community feels that request quotas/throttling is something that's important enough to build into FOLIO (as opposed to leaving it up to the party hosting the FOLIO instance), it should probably be handled in a common/central place, i.e. OKAPI.
- The solution described in the implementation guide, while I'm sure was more than reasonable at one time, seems like a kludge in this day and age.
- API management software (e.g. Redhat's 3Scale) is more likely to be used in enterprise installations of FOLIO, making this rudimentary throttling obsolete in many cases.
So, I'm closing this as "won't do"
|