MuleSoft Nashik Virtual Meetup#2 - API Led Connectivity Integration:SAGA

1. All contents © MuleSoft, LLC
Integration Patterns – Saga
(Orchestration/Choreography)
07th Aug 2021
[10:00 AM IST]

2. All contents © MuleSoft, LLC 2
Organizers
Jitendra Bafna
MuleSoft Ambassador
Hemant Nehete
Lead Technical Architect
LTI
Tirthankar Kundu
Lead Software Engineer
Persistent Systems

3. All contents © MuleSoft, LLC 3
Speakers
Annasaheb Sunthe
Lead Architect
LTI

4. All contents © MuleSoft, LLC 4
• Introduction
• Pattern Overview
• Use Cases
• Pros and Cons of the pattern
• Q & A
Agenda

5. All contents © MuleSoft, LLC
Introduction
5
Why Saga pattern
• Data Consistency is key
• ACID property
• Overcome shortfall of Tradition patterns

6. All contents © MuleSoft, LLC
Pattern Overview
Service A
Service B
Service C
Controller
Client
The Saga- Orchestration is a
microservices pattern, used
to implement a transaction
that spans across multiple
services by leveraging a
controller (Orchestrator) to
orchestrate the events
SAGA - Orchestration
Event /
Message
Event /
Message
Event /
Message

7. All contents © MuleSoft, LLC
Use Case
SAGA - Orchestration
FriendlyStay is hospitality company which runs chain of hotels across the country. Its
web based monolithic room booking application was not able to scale for business
expansion strategy of adding new consumer channels like mobile app and
aggregators.
New application must scale to growing business needs and provide seamless
experience across consumer channels with data consistency.
Decided to go with MuleSoft CloudHub Anypoint Platform and integrate with new tax
system, payment services and order database

8. All contents © MuleSoft, LLC
Pattern Implementation: Order Process
8
Saga - Orchestration
Order Process API
Tax System API
Payment System
API
Orders DB
System API
Payment System Database
MySQL
Delete Order
Create Order
Sync
Orchestrator
Transaction Coordinator
Sync
Transactional
XA Transaction Support
Sync
Transactional
Compensation
Transactions
Sync
Transactional
Compensation
Transactions
Compensation
Transactions
Cancel, Void
transactions
Tax temporary
Tax saved
Tax voided
Tax committed
Tax cancelled
Auth, Sale
transactions
1
2 3 4
5 6 7
Process Layer
MuleSoft Anypoint Platform
System Layer

9. All contents © MuleSoft, LLC
● Pros:
● Better control over the transaction processing
as it gets executed explicitly via an
Orchestration
● Easier Maintenance and supportability owning
to well defined process
Pattern Considerations
Saga - Orchestration
● Cons:
● Adding or modifying the functionality requires
modification to the centralized Orchestrator,
slightly intrusive
● Eventual consistency
● Distributed development is challenging

10. All contents © MuleSoft, LLC
Conclusion
● SAGA Orchestration fits well in use-cases where complete control over complex
transaction management spanning across multiple services is required
● On the flip side, plugging in new systems and services is slightly complex and some cases
intrusive
● Hybrid model with SAGA - Orchestration and SAGA Choreography
Saga - Orchestration

11. All contents © MuleSoft, LLC
Pattern Overview
Service A
Service
B
Service C
Service
Facade
Client
The Saga - Choreography is a
microservices pattern, used
to implement a transaction or
a process that spans across
multiple services in a
decentralized way
SAGA - Choreography
Event /
Message
Event /
Message
Event /
Message
Event /
Message

12. All contents © MuleSoft, LLC
Use Case
Max Inc is an e-commerce company which runs shops and has online presence. Its monolithic
application is not flexible and scalable. Management want to add new systems like fraud
prevention and analytics systems.
Suggested to go with MuleSoft CloudHub Anypoint Platform and integrate with salesforce,
order database, fraud prevention system and shipment partner
SAGA - Choreography

13. All contents © MuleSoft, LLC
Pattern Implementation: Order process
Saga - Choreography
Experience
APIs
System APIs
Process
APIs
Orders
Experience API
Salesforce
Customers System
API
Orders System
API
Fraud Prevention
System API
Shipment
System API
Orders
Database
MySQL
Fraud Management
System
Subscriber Subscriber Subscriber Subscriber
Order Submitted
Topic
Order Created
Topic
Order Status
Topic
Order
Submitted
Event
Compensation
Transaction
Order
Shipped
Event

14. All contents © MuleSoft, LLC
● Pros:
● Increased reliability, availability and scalability
● Decentralized and easily extensible to add a new
system or a service into the mix
● Inherits all the advantages of a managing and
event-based solution such as - Asynchronous
Communication, Loose Coupling and among
others
Pattern Considerations
Saga - Choreography
● Cons:
● No centralized control over the transaction
processing as it is implicit execution, so tricky to
manage and understand the process, especially
if it spans across many services
● Transaction rollback is complicated as each
service needs to support transaction
rollback(compensation transaction) or two-
phase commit (2PC) if underlying systems
support it
● Eventual consistency

15. All contents © MuleSoft, LLC
Conclusion
● SAGA Choreography fits well in use-cases where coordination across different data
domains is required
● It is easy to plugin new systems and services, perhaps too easy, which makes it
challenging to manage if the number of services increases
● There are some use-cases where SAGA - Orchestration is preferred where transaction
management and rollbacks are critical. In these, you can combine them to create a hybrid
model that will provide us the best of both worlds!
Saga - Choreography

16. All contents © MuleSoft, LLC
Q & A
Any questions?

17. All contents © MuleSoft, LLC

18. All contents © MuleSoft, LLC
Quiz:
A. Saga - Orchestration
B. Saga - Choreography
C. Saga - Stereotype
D. Singleton pattern
1. Which pattern fits well in use-cases where complete control over complex
transaction management spanning across multiple services is required?

19. All contents © MuleSoft, LLC
Quiz:
A. Alternate flow
B. Exception transactions
C. Compensation event
D. Compensating transactions
2. If one transaction fails for some reason, the saga also executes _______________
to undo the impact of the preceding transactions.

20. All contents © MuleSoft, LLC
Quiz:
A. Saga - Orchestration
B. Saga - Choreography
C. Saga - Stereotype
D. Singleton pattern
3. Which pattern fits well in use-cases where coordination across different data
domains is required?

21. All contents © MuleSoft, LLC
Thank you