soa - Service locator - why not use DNS? -


there lot of applications can take role of service locator in distributed environment aka soa. example, zookeeper , consul. why not use dns instead?

  • standard, well-known, stable
  • distributed, fault-tolerant
  • can assign multiple ips same name load balancing in homogeneous clusters
  • can serve additional metadata

so... why not?

sure can use dns. many times should. but, if needs greater dns offers , need build custom on top of it, can check existing tools zookeeper, consul, etcd, eureka , others.

you might decide use them if have problem can solve.

for example, might want detect when service goes down or loses connectivity - , remove affected endpoints list of services. of mentioned tools offer out of box.

there nice writeup spotify relevant topic: https://labs.spotify.com/2013/02/25/in-praise-of-boring-technology


Comments

Popular posts from this blog

javascript - Using jquery append to add option values into a select element not working -

Android soft keyboard reverts to default keyboard on orientation change -

Rendering JButton to get the JCheckBox behavior in a JTable by using images does not update my table -