javascript - What is the proper way of sending many requests to Google Maps Geocoding API?

Question

This question already has answers here: question from:https://stackoverflow.com/questions/65874361/what-is-the-proper-way-of-sending-many-requests-to-google-maps-geocoding-api

Answer 1

Related question:

• OVER_QUERY_LIMIT in Google Maps API v3: How do I pause/delay in Javascript to slow it down?

See:

• Geocoding Addresses Best Practices

This section:

Managing errors and retries

If you get an OVER_QUERY_LIMIT status code as a response, you have exceeded the usage limits for the API. We recommend you try these usage optimization strategies.

• Usage Optimization Strategies

Rate limits
The geocoding service is rate limited to 50 QPS (queries per second), calculated as the sum of client-side and server-side queries.

There is a suggestion in the documentation for the web services: Best Practices Using Google Maps APIs Web Services to use Exponential Backoff:

Exponential Backoff
In rare cases something may go wrong serving your request; you may receive a 4XX or 5XX HTTP response code, or the TCP connection may simply fail somewhere between your client and Google's server. Often it is worthwhile re-trying the request as the followup request may succeed when the original failed. However, it is important not to simply loop repeatedly making requests to Google's servers. This looping behavior can overload the network between your client and Google causing problems for many parties.

A better approach is to retry with increasing delays between attempts. Usually the delay is increased by a multiplicative factor with each attempt, an approach known as Exponential Backoff.