
Create the employee service by bootstrapping a Spring starter project with Maven, configuring group and package, and adding Spring Web, DevTools, Spring Data JPA, and Lombok for a MySQL-backed microservice.
Understand service registry and discovery in microservices, linking department, employee, and account services through a registry server. Use Eureka to register and discover available hostings for scalable routing.
Configure client-side load balancing from the employee service to the department service using a load balancer client and Feign builder with Eureka service discovery.
Update Feign client to call the api gateway service and leverage gateway load balancing, comparing client-side and server-side patterns, with verification via services, Postman, and logs.
Create a git repository for the spring config server, initialize it, and commit the employee surveys properties after copying and renaming the application properties to the employee service.
This course will take you to the learning journey starting from creating the microservice till configuring it with the industry standard cloud technologies. This course is suitable for experienced Java developers as well as those who have little knowledge of Spring framework.
We will first start with creating a simple microservice then we will add entities and dto to the service. Exposing them with controller we will implement repositories and services. After that we will add validations and exception handling to the microservice. Also there will be an assignment for the same with another microservice.
First part can be skipped if anyone want to focus on cloud technologies. Then we will add spring cloud technologies to the course.
Starting with Webclient API we will call one microservice from another. Then by introducing the service registry and discovery we no longer need to maintain the URLs. We will take a look at Open Feign. Adding multiple hosting to microservice needs load balancing the requests between them there we will introduce load balancer. As we will be having multiple hosting there needs a single URL to the user which can be achieved by Spring Cloud Gateway. After introducing the gateway we need resiliency in our services hence introduction to Resilience4J is must. As there will be many calls passing through multiple microservices we will introduce distributed tracing using Spring Sleuth and Zipkin. In the end we will implement Spring Config Server to distribute the configurations across the microservices.