Hi All,
We have group of Java developers, and none of them has good Camunda BPM knowledge.
So, when we would like to implement/automate some business process(let’s say of middle complexity, with for example 4-6 process steps, one of which is human task(for approval), another is reading data from other system using web service, and another is storing the final result in Database ), we could see 2 possible ways:
-
custom Java development - with simple workflow functionality built-in
-
use of light-weight BPM solution like Camunda, Activity or jBPM.
The description of the process above is only an example on which I wanted to show, that we are not talking about very complex proceses, with tens of steps…
I somehow feel, that Camunda(or similar solution) better suits our needs, but I need specific arguments to convince our developers that it would be more efficient (in long term) to learn BPM solution and use it for specific scenarios.
What would you say are features of Camunda that are very often used in implemented processes, and are hard (or would take long time) to implement by our own? So reuse them (in solution like Camunda ) would be far better,then starting from scratch ?
And I am focusing here more on the runtime engine features, then additional features like modelling and monitoring environment.
Thank you for your valuable input