Signals versus Conditionals

[claudio_rio]

This is more a curiosity question. The latest Camunda documentation says this about Signals:

Signals are broadcasted to all partitions, resulting in lots of network traffic. This scales linearly with the number of partitions.

With the (re-)introduction of Conditional Events in Camunda 8.9 I wonder if a process with many checks of the same condition would have the same caveats.

To be more precise in the context, suppose a process that has 15 check points that wait for the same external event before proceeding.

Performance-wise:

Should these checkpoints be implemented using Signal Catch events responding to the same Signal or should the check points be implemented by Conditional Events that wait on the same condition that will be set by a single Message Event?

[zee-bot]

Conditional events are evaluated locally within an instance’s variable scope and don’t broadcast across partitions like signals do, so they should generally avoid the network overhead described for signals. I found the following relevant resources:

• Signals concept - broadcast to all partitions
• Conditional events documentation
• Conditionals concept
• What’s new in Camunda 8.9 - BPMN conditional events
• Signal events documentation

Does this help? If not, can anyone from the community jump in?

---

Hints: Use the Ask AI feature in Camunda’s documentation to chat with AI and get fast help. Report bugs and features in Camuda’s GitHub issue tracker. Trust the process.