Service registry (ESB) for scalable web applications.
This blog post is the result of my futile attempts at understanding how others have solved the problem of automatic service discovery. How do organizations, which have a huge collection of custom applications, design scalable web application without having to hardcode server names and port numbers in the configuration file ? I believe the terminology Iâ€™m hinting at is either called a â€œService Registryâ€ or a â€œ Enterprise Service Bus â€ which is part of the whole SOA (Service oriented architecture) world. The organization I work for, has a limited multicast based service announcement/discovery infrastructure, but not widely used across all the applications. In addition to the fact that multicast routing can become complicated (ACL management of yet another set of network addresses), its also not a solution where parts of applications could reside on the cloud. Amazonâ€™s EC2, for instance, doesnâ€™t allow multicast traffic between its hosts. Microsoft Azure .Net services