Cronflower: run a DAG workflow across your cluster, instead of chaining cron jobs

The problem with plain cron

Every team ends up here. One cron job at 02:00 charges the orders. Another at 02:15 ships them, set fifteen minutes later because that's usually long enough for the first one to finish. There's no real dependency between them, no shared data, and no way to see, after the fact, whether step two ran because step one actually succeeded or just because the clock moved. That's the wall plain cron hits: it schedules single jobs, it can't orchestrate a flow of them.

Introducing cronflower

cronflower is an open-source distributed scheduler for Spring Boot with a web console, and it