News for hackers. Stuff that matters.
Re:Ask HN: Job Scheduling as a service by ddorian43 on Monday November 20, 2017 @06:39AM (#15739232)
But cron isn't highly available/distributed with consistent state/scheduling
Re:Ask HN: Job Scheduling as a service by stephenr on Monday November 20, 2017 @06:50AM (#15739271)
Run cron on all your boxes, have them pull a job at a time from the database. Or shit, go full tilt with a clustered Redis job queue.

All of these are better options than "embed the entire job info in a URL and hand it off to a remote scheduling service".

Re:Ask HN: Job Scheduling as a service by scarface74 on Monday November 20, 2017 @07:35AM (#15739451)
Re:Ask HN: Job Scheduling as a service by stephenr on Monday November 20, 2017 @07:52AM (#15739527)
The user doesn't need a queue though. They just need a process to find posts with a publish date of <= now that aren't published and publish them. That's a one line indempotent sql update statement in any decently architected application.
Re:Ask HN: Job Scheduling as a service by scarface74 on Monday November 20, 2017 @08:24AM (#15739688)
This was the other part of the comment I replied to:

Run cron on all your boxes, have them pull a job at a time from the database. Or shit, go full tilt with a clustered Redis job queue.

You're solving for the example but the original poster noted multiple jobs.