Hello, Team.
I’d like to scale my application with Camunda as part of my proof of concept.
One of my workflows would have to handle the massive load, and I anticipate that the request will be too large to process. It takes about 10K RPS to process.
During my inquiry, I discovered that the background execution and scalability would function similarly to kafka.
Whereas in Kafka, the consumer group would be defined to avoid redundant processing, as well as the partition to share the load on the application level, I could only see the partition here in Camunda. Can somebody advise me on the best strategies to scale my application while minimising duplicate processing?
Also, I have the same generic worker that I use to make outbound calls at various stages of the workflow. How would this affect my application’s scalability?
Is it even advisable to reuse the same worker type in my workflow multiple times?
Thanks & Regards,
Raja Gandharaw.