kogito-runtimes VS zeebe

First, I transformed this Trie Tree implementation into an open-source project, which I called Praecepta (Rules in Latin), so anyone can try it out. Then, I added three modules to it, with a decision table based on a real scenario (blurred input/output values). Each module uses a different framework: Praecepta, Camunda 7, and Kogito (the newest Kie solution for the Cloud).

Please notice this new Drools Quarkus extension is not a replacement for Kogito.

https://jbpm.org, https://kogito.kie.org, and the other projects under the https://kie.org umbrella are also worth looking into. jBPM is the grandfather of several of the Java based BPMN solutions if I'm not mistaken.

Query examples: https://github.com/kiegroup/kogito-runtimes/wiki/Data-Index-Service

You can Ctrl + F (or Command + F) your way through the file, but you have to know what you are looking for.

Zeebe

For this purpose, it's the equivalent of using a sledge hammer to crack a walnut, but I think something like Zeebe could facilitate that

I’m doing a lot of exploratory work with BPMN right now.

I think if your business is largely transactional (think Stripe), there is a lot of value to be had by framing your development as “business process automation”.

The term (and BPMN) has a lot of enterprise baggage, but some of the tools out there [0][1] are well suited to orchestrating services (and people where necessary) as a single automated process. The the ability to build that flow visually using BPMN, and then execute it in a workflow engine where you can monitor it, audit it, and optimize over time is pretty compelling.

Here’s an interesting read on the topic: https://www.infoq.com/articles/events-workflow-automation/

[0] https://github.com/camunda-cloud/zeebe

[1] https://github.com/flowable/flowable-engine

(I have no idea whether ES is used in temporal though… never looked at the code)

[1] https://github.com/camunda-cloud/zeebe

[2] https://temporal.io/