AFAIK there are no rate limiting features provided by RestDataSource itself - either the backend remote services could do this (by returning HTTP 429’s to REST calls) or rate limiting should be thought about in terms of use of GraphQL queries & mutations rather than any backend services.
I am already using one of the rate limiter packages for mutations which works well.
The reason I was asking about the limiter, was because my GraphQL server sends API requests to an emailer service in order to send emails that are dispatched.
It is a result of a mutation but since I can’t predict how many concurrent users might hit this mutation at a time, I was hoping to hear how people handle this.
I just thought about this, would a setTimeout work?
Maybe I can add a setTimeout with await before sending the actual request.