Axonframework: Provide alternatives for QuartzEventScheduler and QuartzDeadlineManager

[NielsDoucet]

Given the current state of the quartz project, are there any plans to provide a different mechanism for persistent jobs?

Context:
https://github.com/quartz-scheduler/quartz/issues/275
https://github.com/quartz-scheduler/quartz/issues/277#issuecomment-438291531

[smcvb]

Thanks for bringing this at our attention. I have heard that quartz was slumbering, but didn't check the repo's for any activity in recent times to be honest.

We are definitely open for a new scheduling mechanism, as there is great value in keeping support for the EventScheulder and DeadlineManager.

Any suggested libraries to tackle such a thing would be much appreciated by the way, @NielsDoucet.
In the mean time, I'll ensure we'll discuss the topic internally as well.

[NielsDoucet]

There seems to be a void in the ecosystem at the moment.
I've been on the lookout for an alternative to quartz for quite a while now, so far no such luck though.

[bilak]

Quartz was released a while ago, is it really problem https://github.com/quartz-scheduler/quartz/releases ?

[NielsDoucet]

Did you read the linked comment? https://github.com/quartz-scheduler/quartz/issues/277#issuecomment-438291531

I contacted terracotta devs and got this respons

"Hello Jarl
With Quartz Scheduler being fully Open Sourced, we do not have a plan to release an update in the immediate future.

We understand the desire of the community to see an updated release version, and would hope that a more active fork can be created and maintained outside of our control.

Fiona O’Shea
IoT Analytics Terracotta Dev West“

[abuijze]

The fact that Quartz seems abandoned is an issue to some extent. Fortunately, the way the QuartzScheduler uses Quartz is very basic, meaning that the versions currently available will most likely suffice for the near future.
However, we do feel the need to look for an alternative. On the mailinglist, someone already suggested that the scheduling itself is fairly simple (Axon doesn't need complex scheduling triggers or flexible jobs), and that a JPA/JDBC based implementation is fairly simple to construct.

[srnm]

Perhaps consider
https://github.com/kagkarlsson/db-scheduler
Persistent cluster-friendly scheduler for Java

It uses 1 db table instead of 11, has a much cleaner API, and spring-boot integration.

[smcvb]

Thanks for the suggestion @srnm, looks interesting! We'll debate the suggestion as soon as this issue is picked up. :+1:

[smcvb]

Currently, this issue has been partially resolved through pull request #1383.
The mentioned PR provides an EventScheduler implementation which uses Axon Server to schedule events.

The DeadlineManager alternative, for which we also envision to use Axon Server, will be postponed to the following release. This is required due to changing prioritization and additional work which needs to proceed an AxonServerDeadlineManager implementation.

[smcvb]

Adjusted priority to a "should" and removed milestone.
This issue requires changes in Axon Server which are less pressing on the list.

Furthermore, it is not feasible that this will be resolved before the desired 4.5 release schedule, hence the milestone removal.
This issue will be reevaluated for the following release.