Thank you for the quick responses, that also tells about the community
Ok, transition probably is more of the state machine terminology, which we are using. But now looking into the workflow direction.
By complexity I mean, there can be 100 or more states/transitions/decision points. Some communicating with external service and communications via Kafka topics.
Now we have series of events coming to our system, each event is passed through a workflow, so in a given time there is a possibility that events can launch the same workflow parallelly and can be in a different state.
And these events can be in thousands/sec/min (for now)
Now wondering, how camunda will behave in these scenarios, in terms of memory/cpu requirements
We also need these workflows to be easy to develop by developers by hooking up to new services and also the business analyst could create those workflows with ease.
All these sounds very much what camunda does already, but I need some more real world examples and opinions on this subject.