Long story short, we give you a way to declare what rate-limiting strategy you want. - You can tell us to immediately fail the whole query right away, - Fail j

Long story short, we give you a way to declare what rate-limiting strategy you want. - You can tell us to immediately fail the whole query right away, - Fail just that sub-part of the query - Back off for that API and try again (delaying your overall query but now you don't have to deal with the failure/rate limit case at all) - Potentially do this for all requests across your app, queuing up the api requests to the service that's rate-limited so that you don't have to worry about reasoning locally/globally about rate-limits. We've found this is the level that developer usually feel comfortable thinking about the trade-offs, rather than in the nitty-gritty implementation steps.