Overview
Bizagi Kafka integration brings event driven integration capabilities to Bizagi. Instead of relying on synchronous request and response communication, Bizagi can participate in architectures where systems exchange information through streams of events.
This article introduces the concepts required to understand how Bizagi interacts with Apache Kafka. It provides the foundation for the specific guides on how Bizagi consumes and produces events.
Event driven architecture
In an event driven architecture, systems do not call each other directly. Instead, they publish events that describe something that happened. Other systems subscribe to those events and react accordingly.
This model provides:
•Loose coupling between systems
•Real time reaction to business changes
•Scalability for high volume scenarios
•Resilience through decoupled execution
Kafka basics
Topics
A topic is a channel where events are published. Producers send messages to topics and consumers read from them.
Topics are not discovered automatically. Their names must be known and configured.
Events and messages
An event represents something that occurred, such as a transaction or a status change. In Kafka, events are stored as messages.
Kafka does not enforce structure. Messages can be JSON, XML, or plain text. However, producers and consumers must agree on the format.
Producers
A producer sends messages to Kafka topics.
Bizagi can act as a producer by publishing events from processes to external systems.
Consumers
A consumer listens to topics and processes messages.
Bizagi can act as a consumer by reacting to incoming events and executing actions.
Consumer Group ID
The Consumer Group ID identifies a consumer in Kafka.
It allows:
•Independent consumption of the same topic
•Load distribution
•Fault tolerance
You can define this value freely.
Offsets
Offsets define the position of a consumer within a topic.
They allow:
•Resuming processing after restarts
•Avoiding unintended duplication
•Choosing where to start reading messages
Message contract
Kafka accepts any message format, but all systems must agree on how to interpret it.
This agreement defines:
•Structure of the message
•Meaning of fields
•Expected content
Bizagi in Kafka
Bizagi can participate in two roles:
•As a consumer that reacts to events
•As a producer that publishes events
In many scenarios, Bizagi performs both roles, enabling full event driven workflows.
Last Updated 7/17/2026 4:13:28 PM