LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestras Condiciones de uso y nuestra Política de privacidad para más información.
LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestra Política de privacidad y nuestras Condiciones de uso para más información.
Understanding the best way to develop and deploy applications is an important consideration for any data-driven organization today. Options such as service-oriented architecture (SOA) and microservices offer valuable flexibility for building and running applications that traditional monolithic approaches don’t. However, it can be difficult to understand the differences between the two in order to identify which is best for your business.
This will guides developers and architects to correct approaches for refactoring enterprise systems in order to take advantage of modern architectural approaches.
Here’s an outline of this slides-
~ Problems with monolith applications
~cMicroservices Architecture style
~ What is Reactive Microservices
~ Principles of Isolation
~ Isolation Techniques
In this session, we will cover the transition of an application from
Monoliths to Service Oriented Architecture to Microservices and ﬁnally
to Reactive Microservices by applying isolation techniques to the
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 speciﬁc function
● Synchronous or asynchronous communication
● Services can be physically separated, independently
deployed and scaled
What are the pros of Service-Oriented
What are the cons of Service-Oriented
What are Microservices?
● Subset of Service Oriented Architecture(SOA)
● Diﬀerent 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.
What are Reactive Microservices?
● The core of Reactive
Microservices is to ﬁnd ways to
create more isolation between
● Reactive microservices follow
principles of isolation using
various isolation techniques.
What is Isolation of State?
● Reactive microservices are accessible through its API only
● It allows microservices to evolve internally without aﬀecting 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
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
What is Bulkheading?
● Failure zones are created
● Failure in one microservice not propagated to
● Thus overall system remain operational
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
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
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
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