Removed Disclaim file and incubating name from artifacts
2 files changed
Saga | 中文
Apache ServiceComb (incubating) Saga is an eventually data consistency solution for micro-service applications. Transactions are commited directly in the try phase and compensated in reverse order in the rollback phase comparing to TCC.
- High availability. The coordinator is stateless and thus can have multiple instances.
- High reliability. All transaction events are stored in database permanently.
- High performance. Transaction events are reported to coordinator via gRPC and transaction payloads are serialized/deserialized by Kyro.
- Low invasion. All you need to do is add 2-3 annotations and the corresponding compensate methods.
- Easy to deploy. All components can boot via docker.
- Support both forward(retry) and backward(compensate) recovery.
Saga is composed of alpha and omega.
- The alpha plays as the coordinator. It is responsible for the management of transactions.
- The omega plays as an agent inside the micro-service. It intercepts incoming/outgoing requests and reports transaction events to alpha.
The following diagram shows the relationships among alpha, omega and services.
See Saga Pack Design for details.
- For Spring Cloud applications, please see Booking Demo for details.
- For Dubbo applications, please see Dubbo Demo for details.
Build and Run the tests from source
- Build the source demo docker image and run all tests
$ mvn clean install -Pdemo,docker
- Current Saga code supports Spring Boot 1.x and Spring Boot 2.x at the same time, saga uses Spring Boot 1.x by default, you can use -Pspring-boot-2 to switch Spring Boot version to 2.x. Since Spring Boot supports JDK9 since 2.x, if you want to build and run test the Saga with JDK9 or JDK10, you need to use the spring-boot-2 profile.
$ mvn clean install -Pdemo,docker,spring-boot-2
How to build and use can refer to User Guide.
Get The Latest Release
See Pull Request Guide for details.
Licensed under an Apache 2.0 license.