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
Consider to have a middleware handler to handle service downgrade for the following scenarios:
API server process unusual, return the unusual information to client directly (not reach the service logic)
API server process unusual, catch the request, return intermediate state to client (could be 3XX http status?) and try the request cache latter.
Found Congestion by monitoring, close core business service & business logic for the flood requests
database pressure, like too many connections request waiting ...,
...
Sometimes, we need the middleware handler return to client directly, sometimes we want to the middleware handler pass the situation parameters to service business handler (by audit info?)
It makes sense to provide a middleware handler just like the rate limit middleware handler. Instead of setting it up based on the number of requests, we need to detect certain conditions on the server to return some error code to block the requests to reach the business handlers.
Consider to have a middleware handler to handle service downgrade for the following scenarios:
API server process unusual, return the unusual information to client directly (not reach the service logic)
API server process unusual, catch the request, return intermediate state to client (could be 3XX http status?) and try the request cache latter.
Found Congestion by monitoring, close core business service & business logic for the flood requests
database pressure, like too many connections request waiting ...,
...
Sometimes, we need the middleware handler return to client directly, sometimes we want to the middleware handler pass the situation parameters to service business handler (by audit info?)
@stevehu Can you please take a look?
The text was updated successfully, but these errors were encountered: