Hi Flowable community,
We like your product very much and we appreciate all the good work you’re doing. We are considering to use Flowable as a central part for reimplementation of one of our products. There are still some questions that we would like to be cleared before we dive into the actual implementation. These are some important facts for our use case:
- there would be a large number of processes (hundreds of thousands) started, but eventually waiting to proceed, using timers
- sometimes the wait times would be changed through configuration update, which would require signalling and updating thousands of timers
- when timers expire, thousands of processes would have to be executed simultaneously, some of them more important than others
Our question here is: is it possible for async executor to run prioritized jobs? What are the best practices when handling such large numbers of jobs?
One possible solution that we thought of was using prioritized message queues. Later we discovered “Message Queue based Async Executor” part in the documentation, which could be extended with something like JMS priorities for example. Is this something you would recommend?