4 ms·

I am surprised to see them advocating Route53 for service discovery. Route53 has a very low API rate limit (5/req/s) where simply loading the web dashboard can

I am surprised to see them advocating Route53 for service discovery. Route53 has a very low API rate limit (5/req/s) where simply loading the web dashboard can effect production use.

andrewguenther 10y ago
What Route53 API calls would your dashboard be making? I believe that calls to the health check API do not actually count against this limit (contrary to the documentation saying that this limit is for all requests)
koolba 10y ago
Where do you see such a rate limit? The only limits I've seen for Route53 are the number of hosted zones (50 by default?) and I don't see why that would be an issue. You'd only need one zone per app environment (dev/qa/prod).
- cthalupa 10y ago
  http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/DNSLimitations.html http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/DNS... >All requests – Five requests per second per AWS account. If you submit more than five requests per second, Amazon Route 53 returns an HTTP 400 error (Bad request). The response header also includes a Code element with a value of Throttling and a Message element with a value of Rate exceeded. Though the general AWS recommendation for API limits is implementing exponential backoff + jitter. http://docs.aws.amazon.com/general/latest/gr/api-retries.html http://docs.aws.amazon.com/general/latest/gr/api-retries.htm...
  - koolba 10y ago
    Interesting. I didn't know about that limit. I suppose you can take it a bit further by batching requests (says up to 100 changes per request) but that would complicate distributed apps where the requests aren't coming from one coordinator.