Service Registry

Overview

Service Registry provides your applications with an implementation of the Service Discovery pattern, one of the key tenets of a microservice-based architecture. Trying to hand-configure each client of a service or adopt some form of access convention can be difficult and prove to be brittle in production. Instead, your applications can use the Service Registry to dynamically discover and call registered services.

Service registry overview

When a client registers with the Service Registry, it provides metadata about itself, such as its host and port. The Registry expects a regular heartbeat message from each service instance. If an instance begins to consistently fail to send the heartbeat, the Service Registry will remove the instance from its registry.

Service Registry is based on Eureka, Netflix’s Service Discovery server and client. For more information about Eureka and about the Service Discovery pattern, see Additional Resources.

Refer to the sample applications in the “greeting” repository to follow along with code in this section.

Was this helpful?
What can we do to improve?
View the source for this page in GitHub