https://github.com/iluwatar/java-design-patterns-web/issues/8 Update pattern categories and tags
This commit is contained in:
@@ -3,12 +3,9 @@ layout: pattern
|
||||
title: Saga
|
||||
folder: saga
|
||||
permalink: /patterns/saga/
|
||||
categories: Behavioral
|
||||
categories: Concurrency
|
||||
tags:
|
||||
- Java
|
||||
- Difficulty-Expert
|
||||
- Idiom
|
||||
- Distributed communication
|
||||
- Cloud distributed
|
||||
---
|
||||
|
||||
## Also known as
|
||||
@@ -40,10 +37,12 @@ This orchestrator can also be though of as a Saga Manager.
|
||||
|
||||
## Applicability
|
||||
Use the Saga pattern, if:
|
||||
|
||||
- you need to perform a group of operations related to different microservices atomically
|
||||
- you need to rollback changes in different places in case of failure one of the operation
|
||||
- you need to take care of data consistency in different places including different databases
|
||||
- you can not use 2PC(two phase commit)
|
||||
|
||||
## Credits
|
||||
- [Pattern: Saga](https://microservices.io/patterns/data/saga.html)
|
||||
|
||||
- [Pattern: Saga](https://microservices.io/patterns/data/saga.html)
|
||||
|
Reference in New Issue
Block a user