Penemuan & Pendaftaran Layanan
Terapkan pendaftaran dan penemuan layanan menggunakan Eureka atau Consul untuk menemukan lokasi layanan secara dinamis.
Penemuan & Pendaftaran Layanan adalah pelajaran Spring Boot 4 Complete Guide gratis di CoddyKit. Ini adalah pelajaran 2 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Spring Boot 4 Complete Guide, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Spring Boot 4 Complete Guide mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
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=falseserver.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/eurekapackage 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
@EnableEurekaClientand configure it.
Next, you'll learn about API Gateways, which often use service discovery to route requests.
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Penemuan & Pendaftaran Layanan” gratis?
Ya — teks lengkap “Penemuan & Pendaftaran Layanan” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Spring Boot 4 Complete Guide, upgrade ke CoddyKit PRO. Kursus Spring Boot 4 Complete Guide mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Penemuan & Pendaftaran Layanan”?
Terapkan pendaftaran dan penemuan layanan menggunakan Eureka atau Consul untuk menemukan lokasi layanan secara dinamis. Kamu berlatih Spring Boot 4 Complete Guide dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Spring Boot 4 Complete Guide?
Tidak diperlukan pengalaman sebelumnya. Spring Boot 4 Complete Guide di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 4.
Berapa lama pelajaran “Penemuan & Pendaftaran Layanan” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Spring Boot 4 Complete Guide ini?
Ya. Setiap pelajaran Spring Boot 4 Complete Guide menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Prinsip & Desain Layanan Mikro
- Penemuan & Pendaftaran Layanan
- Gerbang API dengan Spring Cloud Gateway
- Konfigurasi Terpusat dengan Spring Cloud Config