Isolate Task Handler between Process Definition / Handler

Camunda 7 Topics Discussion & Questions
1

Currently External task handlers have Topic name (Hanlders) which is global across the engine. We have multiple teams sharing the engine and creating applications with process definition and handlers. If even one team accidentally adds a handler with same topic name, it will ruin the process.
We can have naming convention but is there a technical way to restrict it.

I did see this forum but not sure if there is any progress on this - [Multi tenant] Namespace/Domain for workflow and tasks for isolation · Issue #3439 · camunda/zeebe · GitHub

Appreciate the help
thankyou

2

Hi @Sumant_Kumar,

No, there isn’t any technical restriction possible and it would be hard for an engine to decide it. The reuse of existing implementation is a good reason to allow duplicate topic names.

A domain name as prefix of a topic name would be a good separator of distinct service implementations.

Hope this helps, Ingo

3

Thankyou @Ingo_Richtsmeier for your response. Would have been good to have a way to restrict to avoid and accidental damage to process. We will try to leverage naming convention for now.