title: Slowness in the geolocation API
body: <p>I'm working on a project that uses HERE's geolocation service.</p>
  
  <p>The project is basically a feature in our system that will route a list of addresses. This routing will happen every day and will have around 7000 points, at least.</p>
  
  <p>Today we use the HERE service to geolocate these addresses and send them to our routing service. However, we are facing a huge bottleneck in this implementation: Of the 7000 points we use for testing, we were able to send only about 200 to geolocate, if we send a larger number of points, we simply do not receive any more response, nor the return of timeout or anything like that.</p>
  
  <p>About the implementation: we do not send all points in the same request, each point to be geocoded is sent in a request. We adjusted our software to send only four requests per second thinking that there could be a QPS block, but we were not successful in solving the problem. We thought about also implementing a massage queue, but this could end up increasing the total time of geolocation + routing, which for us makes the solution unfeasible.</p>
  
  <p>In the code, we have an array that stores the addresses to be geocoded, and for each position of the array we execute a GET request for the following URL: <a href="https://geocoder.ls.hereapi.com/6.2/geocode.json?apiKey=TOKEN&amp;searchtext=ADDRESS" rel="nofollow noreferrer">https://geocoder.ls.hereapi.com/6.2/geocode.json?apiKey=TOKEN&amp;searchtext=ADDRESS</a></p>
  
  <p>If you can help me find a solution.</p>