![Correlating logs Con’t
There are four entries inside braces [] generated by Spring Cloud Stream. The
most important for us is the second entry, which indicates on traceId, that is set
once per incoming HTTP request on the edge of the system.](https://image.slidesharecdn.com/microserviceswithspringbooteurekaandspring-180914093019/85/Microservices-Platform-with-Spring-Boot-Spring-Cloud-Config-Spring-Cloud-Netflix-Eureka-Service-Registry-Netflix-Zull-Gateway-and-Swagger-UI-25-320.jpg)
Microservices Platform with Spring Boot, Spring Cloud Config, Spring Cloud Netflix Eureka Service Registry, Netflix Zull Gateway and Swagger UI
- 1. Microservices with Spring Boot, Eureka and Spring Cloud Prepared By @TIN LINN SOE
- 2. Spring Cloud Related Component Using Spring Boot in cloud-native development Providing Service Registry for all microservices with Spring Cloud Netflix Eureka Distributed configuration with Spring Cloud Config API Gateway pattern using a new project inside Spring Cloud: Spring Cloud Netflix Zull Proxy (Gateway) Spring Cloud Netflix Feign for communication between Microservices Correlating logs with Spring Cloud Sleuth
- 5. Spring Cloud Microservice Architecture
- 6. Spring Cloud Config Server
- 7. Spring Cloud -> Netflix Euraka Registry Server
- 8. Spring Cloud -> Netflix Zuul Proxy (Gateway)
- 9. Demonstration We have three independent microservices which register themself in service discovery fetch properties from configuration service and communicate with each other. The whole system is hidden behind API gateway.
- 10. let’s take a look on the diagram. It illustrates the architecture of our sample demonstration.
- 11. Communication between microservice with Spring Cloud -> Netflix Feign
- 13. Each service is defined their related configuration in Config Server
- 14. Config Server running on Port 8088 Configurations is stored in memory
- 15. Employee Service retrieve configuration from Config Server
- 16. Spring Cloud Netflix Feign for communication between Microservices
- 17. Enabling API specification on gateway using Swagger2 on Zuul Proxy(Gateway) http://localhost:8060/swagger-ui.html.
- 19. Running applications (1) After starting organization-service connects to config-service available under address localhost:8088 (2) Basing on remote configuration settings it is able to register itself in Eureka (3) When the endpoint of organization-service is invoked by external client via gateway (4) available under address localhost:8060, the request is forwarded to instance of organization-service basing on entries from service discovery (5) Then organization-service lookup for address of department-service in Eureka (6) and call its endpoint (7) Finally department-service calls endpont from employee-service. The request as load balanced between two available instance of employee-service by Ribbon
- 21. Let’s take a look on the Eureka Dashboard available under address http://localhost:8061.
- 23. Now, let’s call endpoint http://localhost:8060/organization/1/with- departments-and-employees
- 24. Correlating logs between independent microservices using Spring Cloud Sleuth
- 25. Correlating logs Con’t There are four entries inside braces [] generated by Spring Cloud Stream. The most important for us is the second entry, which indicates on traceId, that is set once per incoming HTTP request on the edge of the system.
- 26. Reference http://projects.spring.io/spring-cloud/ https://piotrminkowski.wordpress.com/2018/04/26/quick-guide-to- microservices-with-spring-boot-2-0-eureka-and-spring-cloud/ https://github.com/piomin/sample-spring-microservices-new
- 27. THANK YOU Next Agenda Hystrix Circuit Breaker Spring Cloud Sleuth (Distributed Tracing)