Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Domain-Driven Refactoring

You're reading from   Domain-Driven Refactoring A hands-on DDD guide to transforming monoliths into modular systems and microservices

Arrow left icon
Product type Paperback
Published in May 2025
Publisher Packt
ISBN-13 9781835889107
Length 324 pages
Edition 1st Edition
Arrow right icon
Authors (2):
Arrow left icon
Alessandro Colla Alessandro Colla
Author Profile Icon Alessandro Colla
Alessandro Colla
Alberto Acerbis Alberto Acerbis
Author Profile Icon Alberto Acerbis
Alberto Acerbis
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Part 1: Why Use Domain-Driven Design to Tackle Complexity?
2. Evolution of Domain-Driven Design FREE CHAPTER 3. Understanding Complexity: Problem and Solution Space 4. Strategic Patterns 5. Tactical Patterns 6. Part 2: Refactoring Legacy Systems
7. Introducing Refactoring Principles 8. Transitioning from Chaos 9. Integrating Events with CQRS 10. Refactoring the Database 11. DDD Patterns for Continuous Integration and Continuous Refactoring 12. Part 3: Moving from Monolith to Microservices
13. When and Why You Should Transition to a Microservices Architecture 14. Dealing with Events and Their Evolution 15. Orchestrating Complexity: Advanced Approaches to Business Processes 16. Other Books You May Enjoy
17. Index

Understanding the difference between process managers and sagas

Saga and process managers are often mistaken to be the same, but they serve distinct purposes. While both handle business processes in distributed systems, they operate differently.

Both Saga and Process Manager are patterns designed to handle long-running, distributed transactions, ensuring consistency across multiple services. However, they differ significantly in how they coordinate the workflow and manage state transitions. The process manager topic is an extensive one and falls beyond the scope of this book. We will focus only on the Saga pattern and how it differs from Process Manager. As an example, Figure 12.6 shows how Process Manager would work applied to our ERP process.

Figure 12.6 – Process Manager for our ERP

Figure 12.6 – Process Manager for our ERP

An incoming message, usually called a trigger message, initializes the process. Based on the rules inside the process manager, it sends a message to the first service, or processing...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime
Visually different images