Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
1–10 of 23 posts
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#2For folks who are using Consul or Zookeeper, would you consider replacing service discovery with this?
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#3For folks who are using Consul or Zookeeper, would you consider replacing service discovery with this?
Not yet. I think this is just the first step towards an AWS-native service mesh solution. I suspect there will be future announcements over the coming months that continue to put all the pieces together.
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#4This 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 number of instances quickly.
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#5Only 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
#6Only 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.
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#7Only 8 records per answer? I wonder why. Many of us run services comprising hundreds of endpoints or more.
It seems to me up to 8 records (ie. 8 IPs) per endpoint (like "api.mysuperwebsite.com" will return up to 8 IPs that can serve the request for that endpoint). That would mean that you can have hundreds of endpoints, but each of them would return up to 8 records. I wonder if there are more than 8 corresponding IPs, how the returned ones are selected (besides the health check), but that's a different question, I guess.
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#8[deleted]
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#9For folks who are using Consul or Zookeeper, would you consider replacing service discovery with this?
Not yet. I think this is just the first step towards an AWS-native service mesh solution. I suspect there will be future announcements over the coming months that continue to put all the pieces together.
[deleted]
Re: Amazon Route 53 Releases Auto Naming API for Service Name Management/Discovery
#10It'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.