Member-only story
Building Microservices [PART-2]: Service Registry & API Gateway Implementations with JWT Authentication
Welcome Back to DevZees ❤
In the part -1 of this microservices series, we developed and tested three services (healthprovider-service, appointment-service and auth-service). Now, let’s move on to the next phase, where we will cover Service Registry and Discovery, as well as the API Gateway. We will register all three microservices with the Service Registry, and later, once we develop the API Gateway, we will register it as well.
✅ Building Microservices [PART-1]: Inter-Service Communication with RestClient & HttpInterface, and Securing with JWT
👁️ Pay Attention: If you’re not a Medium member, you can read it for free here.
✅ Service Registry & Discovery (Eureka Server)
Service Registry & Discovery (Eureka Server) is a vital component in a microservices architecture. It acts as a central hub where all microservices register themselves upon startup. This allows services to discover each other dynamically, facilitating communication without hardcoding service URLs (If you remember from part-1, when the Appointment Service communicated with the Health Provider Service, we hardcoded the Health Provider Service URL. After registering all services with the Eureka Server, we will use the service name instead of hardcoding the direct URL). There are many service registries available, but I will be using Eureka Server because it integrates seamlessly with Spring Cloud, making it easy to set up and manage. Additionally, its easy-to-use dashboard helps monitor registered services, making it a convenient choice for managing microservices in a distributed system.
Eureka Server is a specific implementation of a service registry and discovery tool developed by Netflix, and it is commonly used in Spring Cloud for microservice architectures.
