A commonly agreed core of the approach is the framework required for microservices to notify and communicate with other services. For example Lori McVittie discusses the design principles, highlighting the central role of Service Registries and how they may need a dual high availability architecture.

Service registries, for the uninitiated, are kind of like the internal DNS of a microservices environment. They’re needed to manage the rapid association and disassociation with IP addresses of the containers in which the microservices are typically (but not always) hosted.

Netflix OSS modules for implementing service registries includes dynamic discovery with Eureka. Other technologies include Apache Zookeeper, which can be used for registries as Arun Gupta describes.