Découverte et enregistrement des services

In microservices, applications are broken into many small, independent services. How do these services find each other to communicate? This is where Service Discovery comes in.

It's a key pattern that helps services locate each other automatically. Without it, managing service addresses manually would be a nightmare!

Imagine you have a 'Product Service' and an 'Order Service'. If the Order Service needs to call the Product Service, it needs its network location (IP address and port).

• Manual Configuration: Hardcoding addresses means constant updates if a service moves or scales.
• Scaling Issues: When you add more instances of a service, how do others know about them?
• Resilience: What if a service instance fails? Others need to know to avoid it.

Service discovery solves these problems dynamically.

A Service Registry is like a phone book for your microservices. It's a central database that holds the network locations of all running service instances.

When a service starts up, it registers itself with the registry. When another service needs to communicate, it queries the registry to find an available instance.

Popular service registries include Netflix Eureka, Consul, and Apache ZooKeeper.

Services can register themselves in two main ways:

• Client-Side Registration: The service itself registers and deregisters with the registry. This is common with Eureka.
• Server-Side Registration: A third-party component (like a load balancer or a container orchestrator) registers services on their behalf.

Once registered, services also send periodic 'heartbeats' to the registry to confirm they are still alive and healthy.

Netflix Eureka is a popular service registry developed by Netflix. It's a simple, robust, and highly available registry for microservices.

Eureka consists of two main parts:

• Eureka Server: The central registry that services register with.
• Eureka Client: A library embedded in microservices to interact with the server (register, discover).

It's designed for resilience, prioritizing availability over consistency (AP in CAP theorem).

Let's create a basic Eureka Server. First, add the spring-cloud-starter-netflix-eureka-server dependency. Then, use @EnableEurekaServer on your main application class.

For our Eureka server to run correctly, we need to configure its port and tell it not to register itself (as it's the server). Add these lines to application.properties:

server.port=8761
eureka.client.register-with-eureka=false
eureka.client.fetch-registry=false

server.port=8761 is the default port for Eureka. The other two properties prevent the server from trying to register with itself, which isn't necessary.

Now, let's make a microservice register itself with our Eureka Server. This service becomes a Eureka Client.

First, add the spring-cloud-starter-netflix-eureka-client dependency to your service's project. Then, annotate your main application class with @EnableEurekaClient.

This tells Spring Boot to enable Eureka client features for this application.

Here's how a simple microservice looks with Eureka Client enabled. Notice the @EnableEurekaClient. In its application.properties, you'd define its name and the Eureka server URL:

spring.application.name=product-service
eureka.client.service-url.defaultZone=http://localhost:8761/eureka

Once services are registered, other clients can discover them. Spring Cloud provides DiscoveryClient and RestTemplate (with @LoadBalanced) or WebClient to achieve this.

The client doesn't need to know the exact IP/port. It just asks Eureka for a service by its registered name (e.g., "product-service"). Eureka returns available instances, and a client-side load balancer picks one.

We've explored Service Discovery, a vital pattern for microservices. We learned:

• Why a central Service Registry is needed to avoid hardcoding addresses.
• How Netflix Eureka acts as a registry with its Server and Client components.
• How to set up a Eureka Server using @EnableEurekaServer.
• How to register a microservice as a Eureka Client using @EnableEurekaClient and configure it.

Next, you'll learn about API Gateways, which often use service discovery to route requests.