We are migrating from a legacy OrderMangement system to Camunda in the telecom domain. We have a deadline to meet.
- As part of this we are evaluation a spring boot implementation of camunda.
2.We have more than 50-70 processes in the current legacy implementation.
3.Now we have to migrate all these to Camunda within 6 months
While modeling a particular process flow in camunda we were planning to just create one process and add all the code for 50-70 processes as part this single process to keep it simple at first.(Not worry about whether to use connectors or external tasks or gateways to save time)
Now there are 2 parts a. Workflow in Modeler b. Backend code in the springboot application.
Does the size of workflow diagram (not the code) that gets created add to the complexity.?? Will creating 1 single process make it simpler to start off things.?
Is keeping everything to a single process a good idea from a design and performance perspective? What are the pros and cons?
3.We will ofcourse extend the single process at a later stage and expand. Will this rengineering to be done later be more costly and complex to do.??