Spring Boot 4 Complete Guide · Lesson

Service Discovery & Registration

Implement service registration and discovery using Eureka or Consul for dynamic service location.

Service Discovery & Registration is a free Spring Boot 4 Complete Guide lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Spring Boot 4 Complete Guide learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

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.

Frequently asked questions

Is the “Service Discovery & Registration” lesson free?

Yes — the full text of “Service Discovery & Registration” is free to read here on the web, and the Spring Boot 4 Complete Guide course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Spring Boot 4 Complete Guide course, upgrade to CoddyKit PRO.

What will I learn in “Service Discovery & Registration”?

Implement service registration and discovery using Eureka or Consul for dynamic service location. You practise Spring Boot 4 Complete Guide with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Spring Boot 4 Complete Guide?

No prior experience is required. Spring Boot 4 Complete Guide on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Service Discovery & Registration” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Spring Boot 4 Complete Guide lesson?

Yes. Every Spring Boot 4 Complete Guide lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

Microservices Principles & Design
Service Discovery & Registration
API Gateway with Spring Cloud Gateway
Centralized Configuration with Spring Cloud Config

← Back to Spring Boot 4 Complete Guide