I am quite new on camunda… so bear with me for something that may look obvious.
I try to figure out the use case for embedded BPM architecture model. My guess is that the workflow state in embedded deployment model is only kept in memory of the hosting process( e.g. spring boot web), and there is no data persistence to the database. Correct?
If so, the use case for embedded BPM is only to orchestrate the java classes within the same process, correct?
Appreciate any input.
Hi @emailtowalter,
the use case for the embedded engine is to couple the process logic and the glue code to invoke business services in a single project. The state of the process instances are save in a SQL database.
You can use all BPMN elements and even include html forms to build user tasks in the process.
Finally this can become a real business application with additinal business service endpoints and user forms, hiding the process logic from the user and exposing it only to operators via Cockpit.
It’s not limited, a lot is possible here.
But all code is written in Java, thats true.
Hope this helps, Ingo