hard20 pts · first answer countsresilienceload-shedding

What to drop when overloaded

A checkout service is overloaded. Requests include payment calls from users, background price-cache refreshes and analytics events. What is the best load shedding strategy?

A.Reject requests at random so every caller is treated equallyB.Tag requests with criticality and reject the lowest tiers early, at the edge, before they use expensive resourcesC.Accept everything and let the queue grow until memory runs outD.Shed the oldest payment requests first because they are most likely to time out

Discussion 0

Join free to post in the discussion.

What to drop when overloaded

Discussion 0

Related questions