Distributed job scheduling

Cronflower trades Quartz's lock table for a scheduler cluster you run yourself

The posts show a two-process design: your app declares tasks with @Task, and a separate stateful scheduler cluster owns the schedule and enforces retry, timeout and misfire policy from outside your code.