Microservice Architecture with Spring Cloud in Code

1. Overview

Microservice is a service-oriented architecture where an application is deployed as a collection of loosely-couple services. The goal is to make each service independent, fine-grained, scalable and flexible, allowing faster testing and release.

2. Microservices

2.1 Business Services

2.1.1 applicant-services

Dummy service that returns a list of applicant names.

public List<String> getApplicantsByJob() {

	log.debug("port={} get applicants by job", port);
	return Arrays.asList("Steve", "Bill", "Linus");

2.1.2 job-services

Dummy service that returns a job title with a list of applicant names.

public ResponseEntity listJobsWithApplicantProfiles() {

	log.debug("get job details with applicants");

	JobWithApplicantsDto result = new JobWithApplicantsDto();
	result.setJob("Java Developer");


	return ResponseEntity.ok().body(result);

2.2 Spring Cloud Services

2.2.1 naming-server / discovery-server

This server holds all the information about our microservices, such as name, IP, and port. This information is used for exchanging a service name for IP address and port.

A simple naming server typically has the following:

// pom.xml

// in application.yml
    register-with-eureka: false
    fetch-registry: false

// in SpringBootApplication annotated class

2.2.2 api-gateway

It's a server that provides criteria-driven request routing. It also offers other features such as security, load balancing, logging, monitoring, etc.

API Gateway is not at all different from the naming-server. Thanks to Spring for doing the heavy lifting:

// pom.xml

// @Configuration annotated class
public RouteLocator gatewayRouter(RouteLocatorBuilder builder) {

	return builder.routes()
	    .route(p -> p
	    .route(p -> p.path("/applicants/**")
	    .route(p -> p.path("/jobs/**")

3. Spring Cloud Libraries

3.1 spring-cloud-starter-openfeign - this library is used for referencing service in the naming server

To enable this feature, @EnableFeignClients must be annotated to a configuration class.

To call an endpoint from another service, an interface must be created with the same method signature as the method from the other service. In this example, we are importing 2 endpoints from the applicant-service.

@FeignClient(name = "applicant-services")
public interface ApplicantProxy {

	List<String> getApplicantsByJob();

	public List<String> getTopApplicantsByJob();
3.2 spring-cloud-starter-netflix-eureka-client - this library provides the necessary classes for our services to register to the discovery server.

To register to a naming-server, we need to add this configuration in each of the services:

      defaultZone: http://localhost:8761/eureka // make sure that this address is correct
3.3 spring-cloud-starter-sleuth - this library helps us trace our requests across different microservices by automatically adding a unique id to the logs.

As we can see in the logs, it started from api-gateway, pass thru job-services, and then application-services. In the 3 logs, notice the unique common id: 3b4039e47fb602a9. We can use this when tracing a request.

4. URLs

4.1 Eureka Server

4.2 Applicant Services

4.3 Job Services

4.4 API Gateway

5. Git Repository


6. Summary

This blog teaches the basics of microservice composition and the tools we can leverage to set up such infrastructure. A more in-depth explanation and demonstration are in the video.


spring-microservice 8769951987141480840

Post a Comment Default Comments