Rest Vs. Reactive Interaction Patterns in Microservices Architecture
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Rest Vs. Reactive
Interaction Patterns in Microservices Architecture
IT Consulting
Microservices
System is not very Responsive
API G
atew
ay
Create Order
Inventory Services
Price Services
Payment Services
Shipping Services
Analytics Services
Synchronous and Rest based Architecture
Potential Performance Drawbacks
! I/O & DB blocking !Monoliths and performance management !Poor internal and external end-point
management
Reactive Architecture
!Architecture Style !Responsive !Resilient !Elastic !Message and Event Driven !Asynchronous & non-blocking
API G
atew
ay
Order Management
Service
Inventory Services
Price Services
Payment Services
Shipping Services
Non-blocking and Asynchronous Inter-Service Communication
Order Management
Service Message Broker
C
C
E
E
C Command E Event
Rest
Analytics Services
The Actor Model and the Akka ToolKit
Less-blocking Persistence, DDD, CQRS and Event Sourcing
E Event
ProducerProducer
Event Subscriber
Event Processor
Event Store Journal
E
E
E
E
QueryQuery State
Reinventing the Wheel
!DDD, CQRS and Event Sourcing !Kafka !Actor !Akka !Lagom
Potential Concerns
!Business Process Changes !More complex DevOps !Learning Curve
The rise of the Microservices frameworks
Image Copyright Lightbend
Thank You
Related Documents
