SCB-1235 Clean up the third party license information
4 files changed
tree: 5024fc970d35ff98b0d81c69d426c399fb262de0
  1. .github/
  2. .mvn/
  3. acceptance-tests/
  4. alpha/
  5. demo/
  6. distribution/
  7. docker-build-config/
  8. docs/
  9. integration-tests/
  10. omega/
  11. pack-common/
  12. pack-contracts/
  13. persistence/
  14. scripts/
  15. web/
  16. .gitignore
  17. .travis.settings.xml
  18. .travis.yml
  23. mvnw
  24. mvnw.cmd
  25. NOTICE
  26. pom.xml

Pack | 中文 Build Status Coverage StatusMaven Central License Gitter

Apache ServiceComb Pack is an eventually data consistency solution for micro-service applications.


  • 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.
  • Easy to extend other coordination protocol which is based on the Pack, now we have Saga and TCC support out of box.


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

In this way, we can implement different coordination protocols, such as saga and TCC. See ServiceComb Pack Design for details.

Now we have different lanaguage implementation of Omega

Get Started

  • For ServiceComb Java Chassis application, please see Booking Demo for details.
  • For Spring applications, please see Booking Demo for details.
  • For Dubbo applications, please see Dubbo Demo for details.
  • For TCC with Spring application, please see Tcc Demo for details.
  • To debug the applications, please see Spring Demo Debugging for details.

Build and Run the tests from source

Current ServiceComb Pack code supports Spring Boot 1.x and Spring Boot 2.x at the same time, you can use -Pspring-boot-1, -Pspring-boot-1 to switch Spring Boot version. Since Spring Boot supports JDK9+ from 2.x, if you want to build and run tests of ServiceComb Pack with JDK9 or JDK10, please use the spring-boot-2 profile. Please run the flowing comment from the root directory of ServiceComb Pack.

  • Build the source code and run the tests
       $ mvn clean install -Pspring-boot-2
  • Build the source demo docker images and run the accept tests
       $ mvn clean install -Pdemo,spring-boot-2
  • Build the source code and docker images without running tests, the docker profile will be activated if the maven detects the docker installation.
       $ mvn clean install -DskipTests=true -Pdemo,spring-boot-2
  • Build the release kit for distribution without running the tests, then you can find the release kits in the distribution/target directory.
       $ mvn clean install -DskipTests=true -Prelease

User Guide

How to build and use can refer to User Guide.

Get The Latest Version

Get released version:

Get snapshot version:

  • We publish the snapshot version to Apache nexus repo, please add below repositories into your pom.xml.
                <releases />
                <releases />


Contact Us


See Pull Request Guide for details.

Stargazers over time

Stargazers over time


Licensed under an Apache 2.0 license.