0Pricing
Spring Boot 4 Complete Guide · Lezione

Service discovery e registrazione

Implementare la registrazione e la ricerca dei servizi usando Eureka o Consul per individuare dinamicamente i servizi.

Service discovery e registrazione è una lezione Spring Boot 4 Complete Guide gratuita su CoddyKit. Questa è la lezione 2 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Spring Boot 4 Complete Guide, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Spring Boot 4 Complete Guide include 4 lezioni in totale.

Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.

What is Service Discovery?

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!

Why Manual Addresses Fail

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.

Enter the Service Registry

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.

How Service Registration Works

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.

Meet Netflix Eureka

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).

Building a Eureka Server

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.

package com.coddykit.eurekaserver;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.cloud.netflix.eureka.server.EnableEurekaServer;

@SpringBootApplication
@EnableEurekaServer
public class EurekaServerApplication {
    public static void main(String[] args) {
        SpringApplication.run(EurekaServerApplication.class, args);
    }
}

Configuring Eureka Server

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.

Making a Service Discoverable

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.

Configuring a Eureka Client

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
package com.coddykit.productservice;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.cloud.netflix.eureka.EnableEurekaClient;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;

@SpringBootApplication
@EnableEurekaClient
@RestController
public class ProductServiceApplication {
    public static void main(String[] args) {
        SpringApplication.run(ProductServiceApplication.class, args);
    }

    @GetMapping("/products")
    public String getProducts() {
        return "List of products from Product Service";
    }
}

Discovering Services with 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.

Check Your Understanding

You've learned about setting up a Eureka Server and registering a client. Which annotation is essential for turning a Spring Boot application into a Eureka client?

Recap: Service Discovery

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.

Domande Frequenti

La lezione «Service discovery e registrazione» è gratuita?

Sì — il testo completo di «Service discovery e registrazione» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Spring Boot 4 Complete Guide, passa a CoddyKit PRO. Il corso Spring Boot 4 Complete Guide include 4 lezioni in totale.

Cosa imparerò in «Service discovery e registrazione»?

Implementare la registrazione e la ricerca dei servizi usando Eureka o Consul per individuare dinamicamente i servizi. Eserciti Spring Boot 4 Complete Guide con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.

Ho bisogno di esperienza per iniziare Spring Boot 4 Complete Guide?

Non è richiesta alcuna esperienza precedente. Spring Boot 4 Complete Guide su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 2 di 4.

Quanto tempo richiede la lezione «Service discovery e registrazione»?

La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.

Posso scrivere ed eseguire codice in questa lezione Spring Boot 4 Complete Guide?

Sì. Ogni lezione Spring Boot 4 Complete Guide include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.

Tutte le lezioni di questo corso

  1. Principi e progettazione dei microservizi
  2. Service discovery e registrazione
  3. API Gateway con Spring Cloud Gateway
  4. Configurazione centralizzata con Spring Cloud Config
← Torna a Spring Boot 4 Complete Guide