I’m a little bit confused about the differences between Zeebe and Camunda. I just want to make sure my thoughts are right about these two. At this moment I locally installed Zeebe as the workflow engine. To be able to create and execute BPMN workflows I also installed the following libs:
- BPMN-js → ofcourse for the bpmn workflow moddeling
- zeebe-bpmn-moddle → zeebe-bpmn-moddle
- bpmn-js-properties-panel → to configure task propperties
- other dependencies → not important for this post
for the proppertiespanel I used the zeebePropertiesProviderModule instead of the camunda propertiesProviderModule to create a compliant Zeebe (executable) BPMN workflow. furthermore I use the python client “zeebe-grpc” zeebe-grpc · PyPI to handle all tasks
I’ve two questions:
Regarding npm, for bpmn-js-properties-panel (extract-process-variables) the camunda-bpmn-moddle has to be installed. Instead I installed “zeebe-bpmn-moddle” v0.7.0.
I don’t understand why I should need the camunda-bpmn-moddle if I already installed zeebe-bpmn-moddle? As far as I understand there are three moddle libraries. “camunda-bpmn-moddle”, “zeebe-bpmn-moddle” and “bpmn-moddle”. Are the differents between zeebe and camunda the namespace extensions, meaning that zeebe-bpmn-moddle is used for zeebe and camunda-bpmn-moddle is used for camunda? and is de bpmn-moddle different from zeebe and camunda because of it simply doenst have any namespace extensions what means that it’s not usable for workflow execution?
If the above theory is right, than is it also possible to use camunda-bpmn-moddle with the camunda proppertiesprovider for the proppertiespanel to execute these together in zeebe? In the Camunda Modeler (desktop version) I saw it was also possible to create service tasks as external, meaning that this also should be able to communicate with the python client or maybe Kafka for microservices???