Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?


Failed to load latest commit information.
Latest commit message
Commit time
May 7, 2023 23:08
April 3, 2020 15:26
February 27, 2023 20:10
May 7, 2023 23:22
October 22, 2017 21:12
October 22, 2017 21:12
April 7, 2022 14:21
October 22, 2017 21:12

An Eventuate project


This project is part of Eventuate, which is a microservices collaboration platform.

Eventuate Tram Sagas


eventuate tram sagas bom


eventuate tram sagas quarkus bom

The Eventuate Tram Sagas framework is a saga framework for Java microservices that use JDBC/JPA and Spring Boot/Micronaut.

A major challenge when implementing business applications using the microservice architecture is maintaining data consistency across services. Each service has its own private data and you can’t use distributed transactions. The solution is to use sagas.

A saga maintains consistency across multiple microservices by using a series of a local transactions that are coordinated using messages or events. A saga consists of a series of steps. Each step consists of either transaction, a compensating transaction or both. Each transaction is the invocation of a saga participant using a command message. A saga executes the forward transactions sequentially. If one of them fails then the saga executes the compensating transactions in reverse order to rollback the saga.

Eventuate Tram Sagas is a saga orchestration framework for Spring Boot, Micronaut and Quarkus (using Eventuate Tram for Quarkus) applications. It is built on the Eventuate Tram framework, which enables an application to atomically update a database and publish a message without using JTA. Eventuate Tram Sagas is described in more detail in my book Microservice Patterns.

Writing an orchestrator

The Customers and Orders uses a saga to create an Order in the Order Service and reserve credit in the Customer Service. The CreateOrderSaga consists of the following three steps:

  1. The CreateOrderSaga is instantiated after the Order is created. Consequently, the first step is simply a compensating transaction, which is executed in the credit cannot be reserved to reject the order.

  2. Requests the CustomerService to reserve credit for the order. If the reservation is success, the next step is executed. Otherwise, the compensating transactions are executed to roll back the saga.

  3. Approves the order, if the credit is reserved.

Here is part of the definition of CreateOrderSaga.

public class CreateOrderSaga implements SimpleSaga<CreateOrderSagaData> {

  private SagaDefinition<CreateOrderSagaData> sagaDefinition =

  public SagaDefinition<CreateOrderSagaData> getSagaDefinition() {
    return this.sagaDefinition;

  private CommandWithDestination reserveCredit(CreateOrderSagaData data) {
    long orderId = data.getOrderId();
    Long customerId = data.getOrderDetails().getCustomerId();
    Money orderTotal = data.getOrderDetails().getOrderTotal();
    return send(new ReserveCreditCommand(customerId, orderId, orderTotal))


The reserveCredit() creates a message to send to the Customer Service to reserve credit.

Creating an saga orchestrator

The OrderService creates the saga:

public class OrderService {

  private SagaManager<CreateOrderSagaData> createOrderSagaManager;

  private OrderRepository orderRepository;

  public Order createOrder(OrderDetails orderDetails) {
    ResultWithEvents<Order> oe = Order.createOrder(orderDetails);
    Order order = oe.result;;
    CreateOrderSagaData data = new CreateOrderSagaData(order.getId(), orderDetails);
    createOrderSagaManager.create(data, Order.class, order.getId());
    return order;


Writing a saga participant

Here is the CustomerCommandHandler, which handles the command to reserve credit:

public class CustomerCommandHandler {

  private CustomerRepository customerRepository;

  public CommandHandlers commandHandlerDefinitions() {
    return SagaCommandHandlersBuilder
            .onMessage(ReserveCreditCommand.class, this::reserveCredit)

  public Message reserveCredit(CommandMessage<ReserveCreditCommand> cm) {

Maven/Gradle artifacts

The artifacts are in JCenter. The latest version is:





If you are writing a Saga orchestrator add this dependency to your project:

  • io.eventuate.tram.sagas:eventuate-tram-sagas-orchestration-simple-dsl:$eventuateTramSagasVersion

If you are writing a saga participant then add this dependency:

  • io.eventuate.tram.sagas:eventuate-jpa-sagas-framework:$eventuateTramSagasVersion

You must also include one of the Eventuate Tram 'implementation' artifacts:

  • io.eventuate.tram.core:eventuate-tram-jdbc-kafka:$eventuateTramVersion - JDBC database and Apache Kafka message broker

  • io.eventuate.tram.core:eventuate-tram-in-memory:$eventuateTramVersion - In-memory JDBC database and in-memory messaging for testing

Running the CDC service

In addition to a database and message broker, you will need to run the Eventuate Tram CDC service. It reads messages and events inserted into the database and publishes them to Apache Kafka. It is written using Spring Boot. The easiest way to run this service during development is to use Docker Compose. The Eventuate Tram Code Basic examples project has an example docker-compose.yml file.


Contributions are welcome.