Basics of Microservice Architecture
- 1. Basics of Microservice Architecture Presenter: Souvik Ghosh
- 2. TOPICSOFDISCUSSION What is Microservice? What is Monolithic Architecture and It’s Drawbacks Why to Use Microservice Architecture? Challenges in Microservices Implementation and How to Resolve It What is Service Discovery and Eureka? Calling Another Microservice and Load Balancing Use of API Gateway Fault Tolerance With Hystrix Centralized Configuration Using Spring Cloud Config Server A Sample Microservices Architecture
- 3. What are Microservices? Monolithic Architecture Microservices Architecture Application A Application a1 Application a2 Application a3 Application a4
- 4. Drawbacks of Monolithic Architecture 1. Large monolithic code base is very difficult to understand 2. It’s not fault tolerant 3. Overloaded Web Container and Overloaded IDE 4. Frequent deployment is difficult 5. Scaling the application is difficult 6. “A monolithic architecture forces you to be married to the technology stack (and in some cases, to a particular version of the technology) you choose at the start of the development.”
- 5. Why Microservice Architecture? 1. Code base is better understandable 2. Highly maintainable and testable - enables rapid and frequent development and deployment 3. Loosely coupled with other services so independently deployable 4. Improved fault isolation 5. Adapting new technologies is easier 6. The faster IDE makes developer more productive
- 6. Challenges in Microservices Implementation and Solutions Discovering all the running services and their instances Taking care of multiple service calls Finding easier way of load balancing Maintaining configuration of multiple services Monitoring all the incoming requests to all the services Handling Fault Tolerance Eureka Naming Server by Netflix OSS Rest Template by Spring Frameworks Feign Client by Netflix OSS Ribbon by Netflix OSS Spring Cloud Config Server Zuul API Gateway by Netflix OSS Hystrix By Netflix OSS
- 7. What is Service Discovery? Eureka Eureka Naming Server (port:8761) Ms-A (8081) Ms-B (8082) Ms-C (8083) http://localhost :8761 Ms-A running on port 8081 Ms-B running on port 8082 Ms-C running on port 8083 & 8084 Ms-C (8084)
- 8. Calling Another Microservice and Load Balancing Eureka Naming Server Ms-A (9091) Ms-B (9092) Ms-B (9093) Ms-B (9094) Ribbon 2nd call Client
- 9. Use of API Gateway Ms-A Ms-B Ms-C Ms-D Client Zuul API Gateway Server
- 10. Fault Tolerance With Hystrix Faulty Ms-B returns a default output to make the other services safe Ms-A Ms-B (Faulty Service) Ms-C Client
- 11. Centralized Configuration By Config Server Storing All Configurations in a GIT Repository Ms-A Ms-B Ms-C Spring Cloud Config Server GIT Repo
- 13. Thank You