Using Camunda DMN tables in parallel processing
Last time I tackled simple DMN tables using Collect(Sum) policy in demo called Customer Scoring.
Last time I tackled simple DMN tables using Collect(Sum) policy in demo called Customer Scoring.
Next demo shows how to use #Camunda DMN tables for parallel processing and FEEL expressions. No glue, no source code, all on Zeebe side.
The use case fits fictive restaurant scenario for payment and calculates price with additional discount according to total spending.
Project with this demo is available on GitHub.
Last time I tackled simple DMN tables using Collect(Sum) policy in demo called Customer Scoring.
Within this demo we’re going to see once again how Dapr and Camunda Platform 8 works well together and provide language agnostic approach. In this case with...
After some time I went back to Dapr (v10) and Zeebe engine used in Camunda Platform 8. Updated projects to .NET 7 and tried again what I learned before and r...
It’s awesome to see how Dapr and Camunda workflow engine work well together. By using BPMN and DMN we completely remove business logic from the code and only...
One of OOP principles says, that every class should enter valid states only. The bigger class it is, the harder to do. Typically we use class constructors so...
A lot happened this and last year, so why not to share some thoughts and experience from implementing domain driven design on an existing monolithic applicat...