Orchestration-Based Saga

Orchestration-Based Saga sits at the heart of saga pattern in Apache Kafka. This guide walks through the concept step by step, with examples, a cheatsheet, and common mistakes to avoid.

Orchestration-Based Saga Overview

Orchestration-Based Saga is a building block you will reach for often in Apache Kafka. It keeps related logic together and makes your intent obvious to reviewers and future maintainers.

When you learn orchestration-based saga properly, you avoid the guesswork that leads to bugs and rework. The example below shows the shape you will use in most real Apache Kafka projects.

// each service reacts to events and emits new ones
await consumer.subscribe({ topic: 'payment-completed' });
await consumer.run({
  eachMessage: async ({ message }) => {
    const payment = JSON.parse(message.value.toString());
    await producer.send({
      topic: 'order-confirmed',
      messages: [{ key: payment.orderId, value: JSON.stringify(payment) }],
    });
  },
});

Event-driven services stay decoupled by reacting to and emitting Kafka events.

Orchestration-Based Saga Example

import { Kafka } from 'kafkajs';

const kafka = new Kafka({ clientId: 'app', brokers: ['localhost:9092'] });
const producer = kafka.producer();
const consumer = kafka.consumer({ groupId: 'group' });

Start from a minimal Orchestration-Based Saga example and grow it only as needed.
Keep configuration explicit so Orchestration-Based Saga behaves the same in every environment.
Name things clearly so teammates understand your Orchestration-Based Saga at a glance.
Add tests around Orchestration-Based Saga early to lock in expected behaviour.

Apache Kafka Cheatsheet

Handy KafkaJS reference related to orchestration-based saga.

Task	Example	Purpose
Create client	`new Kafka({ clientId, brokers })`	Connect to the cluster
Produce	`producer.send({ topic, messages })`	Publish events
Consume	`consumer.run({ eachMessage })`	Process events
Subscribe	`consumer.subscribe({ topic })`	Choose topics to read
Group	`kafka.consumer({ groupId })`	Scale consumers
Admin	`admin.createTopics(...)`	Manage topics
Commit offset	auto-commit or `commitOffsets`	Track progress

How Orchestration-Based Saga Works in Apache Kafka

Orchestration-Based Saga builds on Kafka's log-based design, where producers append events to partitioned topics and consumer groups read them independently, tracking their own offsets.

Event-driven services stay decoupled by reacting to and emitting Kafka events.

Topics are split into partitions for parallelism and ordering per key.
Producers choose a partition, usually by message key.
Consumer groups share partitions so work scales horizontally.
Offsets record how far each group has read.

Practical Guidance for Orchestration-Based Saga

In production, orchestration-based saga needs attention to delivery guarantees, retries, and observability. Make handlers idempotent and monitor consumer lag closely.

Concern	Recommendation
Ordering	Key related events so they land on one partition
Reliability	Use acks=all and idempotent producers
Idempotency	Handle duplicate deliveries safely
Monitoring	Track consumer lag and error rates

Common Mistakes

Skipping error handling and edge cases when wiring up orchestration-based saga.
Leaving orchestration-based saga untested, so regressions slip into production.
Over-engineering orchestration-based saga before you actually need the extra flexibility.
Ignoring documentation, which makes orchestration-based saga hard for the next developer to change.

Key Takeaways

Orchestration-Based Saga is a core part of working effectively with Apache Kafka.
Start small and keep orchestration-based saga focused on a single responsibility.
Apply consistent patterns so orchestration-based saga scales across your project.
Test and document orchestration-based saga to keep it maintainable over time.

Pro Tip

Pair orchestration-based saga with automated tests from day one. It is far cheaper to catch Apache Kafka regressions in CI than in production.