This seems like a useful feature but it would be nice to have a better understanding of how it affects rate-limiting. Historically Route53 has been pretty useless for service discovery because of the heavy rate-limiting. Something around 5 updates per second, on the whole account with a window of 60 seconds. I don't know if it's still the case but it used to be quite painful, especially when you need to scale up the…
Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
11–20 of 23 posts
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#12This seems like a useful feature but it would be nice to have a better understanding of how it affects rate-limiting. Historically Route53 has been pretty useless for service discovery because of the heavy rate-limiting. Something around 5 updates per second, on the whole account with a window of 60 seconds. I don't know if it's still the case but it used to be quite painful, especially when you need to scale up the…
Why would these instances not be behind ELB?
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#13It's not clear how this is different from what is currently possible. I'm not a route53 guru but can't you already a) create a subdomain microservice.mydomain.com b) create instances c) add the instances IP address to an A or AAAA record for the subdomain. Is it that they didn't have APIs for these operations and now they do? I know I'm missing something.
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#14It's not clear how this is different from what is currently possible. I'm not a route53 guru but can't you already a) create a subdomain microservice.mydomain.com b) create instances c) add the instances IP address to an A or AAAA record for the subdomain. Is it that they didn't have APIs for these operations and now they do? I know I'm missing something.
Now with auto-naming, you create a service[1], then a service instance calls RegisterInstance[2] on start-up with a much simpler JSON payload.
0: https://docs.aws.amazon.com/Route53/latest/APIReference/API_...
1: https://docs.aws.amazon.com/Route53/latest/APIReference/API_...
2: https://docs.aws.amazon.com/Route53/latest/APIReference/API_...
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#15Only 8 records per answer? I wonder why. Many of us run services comprising hundreds of endpoints or more.
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#16It's not clear how this is different from what is currently possible. I'm not a route53 guru but can't you already a) create a subdomain microservice.mydomain.com b) create instances c) add the instances IP address to an A or AAAA record for the subdomain. Is it that they didn't have APIs for these operations and now they do? I know I'm missing something.
The one time I've wanted this is with auto scaling groups for services that don't use ELBs. I haven't found docs on it, but if this could be used to add/remove DNS records based on auto scaling events that would be useful. It would save from using lifecycle hooks to trigger a Lambda function.
Also this seems to be a larger service discovery play, it just doesn't seem very fleshed out yet.
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#17It's not clear how this is different from what is currently possible. I'm not a route53 guru but can't you already a) create a subdomain microservice.mydomain.com b) create instances c) add the instances IP address to an A or AAAA record for the subdomain. Is it that they didn't have APIs for these operations and now they do? I know I'm missing something.
Am I right?
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#18Only 8 records per answer? I wonder why. Many of us run services comprising hundreds of endpoints or more.
Considering this is DNS there has been a historical limit of 512 bytes. Despite this not usually being a limitation now you are really pushing the ideal packet size with hundreds of answers each of which are multiple bytes. High chance of packets being dropped.
Only with UDP transport, longer responses are told to requery via TCP.
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#19This seems like a useful feature but it would be nice to have a better understanding of how it affects rate-limiting. Historically Route53 has been pretty useless for service discovery because of the heavy rate-limiting. Something around 5 updates per second, on the whole account with a window of 60 seconds. I don't know if it's still the case but it used to be quite painful, especially when you need to scale up the…
Why would these instances not be behind ELB?