On the county-council digitalization backend, almost everything important happened on a schedule: digital-certificate verification, batch document processing, and the index maintenance that kept queries fast as data grew.
Why Quartz over a cron
A cron entry is invisible to the application. Quartz jobs live inside the same context, share the same transactions and configuration, and are observable through the same logs and metrics as the rest of the service. For a government system that needs an audit trail, that visibility is not optional.
Keeping jobs safe
Every job was idempotent and every run was logged with enough context to replay it. Schema and view design went hand in hand with the scheduling: the queries the jobs ran drove the indexes I built.