3 ms·
At any reasonable scale you typically wouldn’t use plain DNS if you have to do that kind of figuration. It would be done with a service discovery service which
by matt_wulfeck 9y ago
At any reasonable scale you typically wouldn’t use plain DNS if you have to do that kind of figuration. It would be done with a service discovery service which handles SRV records.
That being said route53 has a reasonable management API.
- cat199 9y agothanks - should have mentioned specifically not looking at cloud services (e.g. self hosted, but without needing 5 different polyglot microservices and a service managment layer and 32GB of ram just to keep the whole mess running) I see 0% need for this complexity in many cases on the presentation side - and if faster response is required internally, the same API IF can be used for service discovery or side-chain announcements, etc can be bolted on on a per-application basis if desired. I also see 0% need for this to be a cloud exclusive domain - e.g. hybrid scope/location deployments, etc.