We are using Saga for managing the timeout of events. We generate around 100 events per second and each event has 2 sec timeout.
We are using JDBC store for Quartz which does not seem to scale even after increasing the processor count in Oracle.
Due to small timeout, we are not able to scale the functionality using Saga. Specifically the locks acquired during quartz job creation.
Do you suggest to use Saga Timeout for internal handling with such small timeout or is there any better way for handling this situation?
Or Is there any specific configuration to be take care at Axon framework level or Oracle Db level to tune this.