本篇文章为你整理了Sagas（sagasf和sa区别）的详细内容，包含有sagasf700 sagasf和sa区别 sagas legends sagasf700c Sagas，希望能帮助你了解 Sagas。
Take a look at my self-paced, online bootcamp that teaches you how to use the Saga, API Composition, and CQRS patterns to design operations that span multiple services.
The regular price is $395/person but use coupon KGBJMRAM to sign up for $195 (valid until March 8th, 2023)
You have applied the Database per Service pattern.
Each service has its own database.
Some business transactions, however, span multiple service so you need a mechanism to implement transactions that span services.
For example, let’s imagine that you are building an e-commerce store where customers have a credit limit.
The application must ensure that a new order will not exceed the customer’s credit limit.
Since Orders and Customers are in different databases owned by different services the application cannot simply use a local ACID transaction.
Problem
How to implement transactions that span services?
Forces
Implement each business transaction that spans multiple services as a saga.
A saga is a sequence of local transactions.
Each local transaction updates the database and publishes a message or event to trigger the next local transaction in the saga.
If a local transaction fails because it violates a business rule then the saga executes a series of compensating transactions that undo the changes that were made by the preceding local transactions.
There are two ways of coordination sagas:
Choreography - each local transaction publishes domain events that trigger local transactions in other services
Orchestration - an orchestrator (object) tells the participants what local transactions to execute
An e-commerce application that uses this approach would create an order using a choreography-based saga that consists of the following steps:
The Order Service receives the POST /orders request and creates an Order in a PENDING state
It then emits an Order Created event
The Customer Service’s event handler attempts to reserve credit
It then emits an event indicating the outcome
The OrderService’s event handler either approves or rejects the Order
An e-commerce application that uses this approach would create an order using an orchestration-based saga that consists of the following steps:
The Order Service receives the POST /orders request and creates the Create Order saga orchestrator
The saga orchestrator creates an Order in the PENDING state
It then sends a Reserve Credit command to the Customer Service
The Customer Service attempts to reserve credit
It then sends back a reply message indicating the outcome
The saga orchestrator either approves or rejects the Order
It enables an application to maintain data consistency across multiple services without using distributed transactions
The programming model is more complex.
For example, a developer must design compensating transactions that explicitly undo changes made earlier in a saga.
In order to be reliable, a service must atomically update its database and publish a message/event.
It cannot use the traditional mechanism of a distributed transaction that spans the database and the message broker.
Instead, it must use one of the patterns listed below.
A client that initiates the saga, which an asynchronous flow, using a synchronous request (e.g. HTTP POST /orders) needs to be able to determine its outcome.
There are several options, each with different trade-offs:
The service sends back a response once the saga completes, e.g. once it receives an OrderApproved or OrderRejected event.
The service sends back a response (e.g. containing the orderID) after initiating the saga and the client periodically polls (e.g. GET /orders/{orderID}) to determine the outcome
The service sends back a response (e.g. containing the orderID) after initiating the saga, and then sends an event (e.g. websocket, web hook, etc) to the client once the saga completes.
A choreography-based saga can publish events using Aggregates and Domain Events
My book Microservices patterns describes this pattern in a lot more detail. The book’s example application implements orchestration-based sagas using the Eventuate Tram Sagas framework
Take a look at my self-paced, online bootcamp that teaches you how to use the Saga, API Composition, and CQRS patterns to design operations that span multiple services.
Read these articles about the Saga pattern
My presentations on sagas and asynchronous microservices.
The following examples implement the customers and orders example in different ways:
Microservices.io is brought to you by Chris Richardson.
Experienced software architect, author of POJOs in Action, the creator of the original CloudFoundry.com, and the author of Microservices patterns.
Chris helps clients around the world adopt the microservice architecture through consulting engagements, and training workshops.
Wondering whether your organization should adopt microservices?
Want to know how to migrate your monolith to microservices?
Facing a tricky microservice architecture design problem?
Consider signing up for a two hour, highly focussed, consulting session.
My virtual bootcamp, distributed data patterns in a microservice architecture, is now open for enrollment!
It covers the key distributed data management patterns including Saga, API Composition, and CQRS.
It consists of video lectures, code labs, and a weekly ask-me-anything video conference repeated in multiple timezones.
The regular price is $395/person but use coupon KGBJMRAM to sign up for $195 (valid until March 8th, 2023).
There are deeper discounts for buying multiple seats.
Chris teaches comprehensive workshops, training classes and bootcamps for executives, architects and developers to help your organization use microservices effectively.
Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and how to refactor a monolith to microservices.
Delivered in-person and remotely.
Example microservices applications
Want to see an example? Check out Chris Richardsons example applications.
See code
Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,
Use the Eventuate.io platform to tackle distributed data management challenges in your microservices architecture.
Eventuate is Chriss latest startup. It makes it easy to use the Saga pattern to manage transactions and the CQRS pattern to implement queries.
Assess your applications microservice architecture and identify what needs to be improved.
Consulting services
Engage Chris to conduct an architectural assessment.
以上就是Sagas（sagasf和sa区别）的详细内容，想要了解更多 Sagas的内容，请持续关注盛行IT软件开发工作室。
郑重声明：本文由网友发布，不代表盛行IT的观点，版权归原作者所有，仅为传播更多信息之目的，如有侵权请联系，我们将第一时间修改或删除，多谢。