In the microservices world, Service Registry and Discovery plays an important role because we most likely run multiple instances of services, and
we need a mechanism to call other services without hardcoding their hostnames or port numbers.
In addition to that, in Cloud environments, service instances may come up and go down at any time.
So we need some automatic service registration and discovery mechanism. Spring Cloud provides Service Registry and Discovery features, as usual,
with multiple options. We can use Netflix Eureka or Consul for Service Registry and Discovery.

Test

A step-by-step guide to implementing Service Registry and Discovery in a Spring Boot microservices architecture using Spring Cloud Netflix Eureka. Covers setting up a standalone Eureka Server, registering microservices as Eureka clients, running multiple service instances, and using a load-balanced RestTemplate with service IDs instead of hardcoded hostnames and ports to invoke inter-service REST calls.

MicroServices - Part 3 : Spring Cloud Service Registry and Discovery

Spring Cloud Netflix Eureka-based Service Registry

Registering microservices as Eureka Clients

Discovering other services using a Eureka Client