Saga 0.1.0 Release
SCB-404 Use different base folder for source and binary package
2 files changed
tree: 31f68aa96931e15841ae8b9ebbb8c9306867be0c
  1. .github/
  2. acceptance-tests/
  3. alpha/
  4. docker-build-config/
  5. docs/
  6. integration-tests/
  7. omega/
  8. pack-common/
  9. pack-contracts/
  10. saga-demo/
  11. saga-distribution/
  12. saga-persistence/
  13. scripts/
  14. .gitignore
  15. .travis.settings.xml
  16. .travis.yml
  18. gpg-sec.tar.enc
  20. NOTICE
  21. pom.xml

Saga | 中文 Build Status Coverage Status License

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. Saga Pack Architecture

See Saga Pack Design for details.

Get Started

See Booking Demo for details.

User Guide

How to build and use can refer to User Guide.


Contact Us


See Pull Request Guide for details.


Licensed under an Apache 2.0 license.