Diving Into Reactive Microservices
0 likes204 views
This document outlines a presentation on reactive microservices by Mansi Babbar from Knoldus, covering the transition from monolithic architectures to service-oriented architecture, microservices, and ultimately to reactive microservices. It describes key concepts such as isolation techniques, principles of isolation, and various architectural patterns including bulkheading, circuit breakers, and message-driven architecture. The document emphasizes the importance of creating more isolation among microservices to enhance scalability and fault tolerance.
Diving Into Reactive Microservices
- 1. Diving Into Reactive Microservices Presented By: Mansi Babbar Software Consultant Knoldus Inc.
- 2. About Knoldus Knoldus is a technology consulting firm with focus on modernizing the digital systems at the pace your business demands. Functional. Reactive. Cloud Native
- 3. 01 Introduction 02 Monoliths 03 Service Oriented Architecture 04 Microservices 05 Reactive Microservices Our Agenda 06 Principles of Isolation 07 Isolation Techniques
- 5. Software Spectrum In this session, we will cover the transition of an application from Monoliths to Service Oriented Architecture to Microservices and finally to Reactive Microservices by applying isolation techniques to the application.
- 8. What is Monolithic Ball of Mud? ● No clear isolation ● Complex dependencies ● Application is harder to understand and modify
- 9. What are Monoliths? ● Deployed as a single unit ● Have a single shared database ● Communicate with synchronous method calls where a message is sent and response is expected immediately.
- 10. What are the cons of Monoliths?
- 12. What is Service-Oriented Architecture? ● Architectural style that structures an application as a collection of smaller independent services ● Each service has its own logic and database as well as performs specific function ● Synchronous or asynchronous communication between services. ● Services can be physically separated, independently deployed and scaled
- 13. What are the pros of Service-Oriented Architecture?
- 14. What are the cons of Service-Oriented Architecture?
- 16. What are Microservices? ● Subset of Service Oriented Architecture(SOA) ● Different from SOA in terms of deployment ● In Microservices, services have to be deployed independently unlike SOA ● Apart from this, Microservices follow all rules provided by SOA.
- 17. What are the pros of Microservices?
- 19. What are Reactive Microservices? ● The core of Reactive Microservices is to find ways to create more isolation between microservices. ● Reactive microservices follow principles of isolation using various isolation techniques.
- 21. What are the Principles of Isolation?
- 22. What is Isolation of State? ● Reactive microservices are accessible through its API only ● It allows microservices to evolve internally without affecting outside What is Isolation in Space? ● Reactive microservices are independently deployed ● The location of a microservice does not impact other microservices ● It allows microservices to be scaled up/down to meet demand
- 23. What is Isolation in Time? ● Reactive microservices are asynchronous and non-blocking ● Eventual consistency is expected between microservices What is Isolation of Failure? ● Reactive microservices also isolate failures ● A failure in one microservice does not cause another to fail ● It allows the system to remain operational in spite of failure
- 25. What are the Isolation Techniques?
- 26. What is Bulkheading? ● Failure zones are created ● Failure in one microservice not propagated to others ● Thus overall system remain operational
- 27. What is Circuit Breaker? ● When a microservice is calling another microservice that is overloaded and that may fail ● The caller microservice may not realize that the called microservice is under heavy load and it may retry ● Results in more load on the called microservice ● Caller microservice needs to be careful to avoid this ● Quarantine the failing service so it can fail fast
- 28. What is Message Driven Architecture? ● Usage of asynchronous non-blocking messaging ● Allows isolation in both time and failure ● If a request to a microservice fails the failure won’t propagate ● Microservices are not dependent on the response from each other
- 29. What is Autonomous Microservice? ● Microservices can guarantee their behaviour using API calls ● Isolation allows a service to operate independently of other services ● Autonomy allows for stronger scalability and availability ● Autonomy can be achieved through asynchronous messages ● Use eventual consistency
- 30. What is API Gateway Service? ● API gateway service receives requests from client and send them further to microservices ● Aggregates the responses from microservices ● Handles failures from each service ● Client has to deal with only gateway service failure.
- 31. References ● https://academy.lightbend.com/courses/course-v1:lightbend+LRA-ReactiveMicr oservices+v1/about ● https://developer.ibm.com/depmodels/reactive-systems/articles/develop-reacti ve-microservices-with-microprofile/ ● https://www.cognizant.com/whitepapers/building-a-high-performance-reactive- microservices-architecture-codex2654.pdf ● https://www.oreilly.com/content/what-is-a-reactive-microservice/