4 ms·

You want cron, as a service? Shit on a stick doesn't anyone actually host anything themselves anymore?

dozzie 9y ago
We do, but it's not sexy, because it just gets the job done and you can't really brag about not having bugs or troubles.
mani-smhack 9y ago
I need a scheduler where i can dynamically ( via api ) schedule a job , with the admin UI to manage the jobs . I Think these are not part of application development and it can be offloaded to hosted services .
- caraga 9y ago
  Jenkins has scheduled jobs and an UI. It can also be accessed via API. https://jenkins.io/ https://jenkins.io/
  - mani-smhack 9y ago
    This is not with respect to devops or build . My app has schedule functionality for example a scheduled report , so if it where like a webhook call then i dont want to waste the cpu cycle ,now i am using quartz scheduler in my java app .
    - aprdm 9y ago
      Jenkins isn't just for devops or build.
- bpicolo 9y ago
  There are a lot of frameworks for this in various languages, depends on what you're doing - like sidekiq in ruby and hangfire in dotnet https://github.com/mperham/sidekiq https://github.com/mperham/sidekiq https://www.hangfire.io/ https://www.hangfire.io/
ddorian43 9y ago
But cron isn't highly available/distributed with consistent state/scheduling
- stephenr 9y ago
  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".
  - scarface74 9y ago
    http://mikehadlow.blogspot.com/2012/04/database-as-queue-anti-pattern.html?m=1 http://mikehadlow.blogspot.com/2012/04/database-as-queue-ant...
    - stephenr 9y ago
      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.
      - scarface74 9y ago
        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.

We do, but it's not sexy, because it just gets the job done and you can't really brag about not having bugs or troubles.

mani-smhack 9y ago

I need a scheduler where i can dynamically ( via api ) schedule a job , with the admin UI to manage the jobs . I Think these are not part of application development and it can be offloaded to hosted services .

caraga 9y ago
Jenkins has scheduled jobs and an UI. It can also be accessed via API. https://jenkins.io/ https://jenkins.io/
- mani-smhack 9y ago
  This is not with respect to devops or build . My app has schedule functionality for example a scheduled report , so if it where like a webhook call then i dont want to waste the cpu cycle ,now i am using quartz scheduler in my java app .
  - aprdm 9y ago
    Jenkins isn't just for devops or build.
bpicolo 9y ago
There are a lot of frameworks for this in various languages, depends on what you're doing - like sidekiq in ruby and hangfire in dotnet https://github.com/mperham/sidekiq https://github.com/mperham/sidekiq https://www.hangfire.io/ https://www.hangfire.io/

ddorian43 9y ago

But cron isn't highly available/distributed with consistent state/scheduling

stephenr 9y ago
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".
- scarface74 9y ago
  http://mikehadlow.blogspot.com/2012/04/database-as-queue-anti-pattern.html?m=1 http://mikehadlow.blogspot.com/2012/04/database-as-queue-ant...
  - stephenr 9y ago
    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.
    - scarface74 9y ago
      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.