Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Posthook – Job Scheduling as a Service

posthook.io

Post reply on HN
Print view View original

21–30 of 76 posts

Re: Show HN: Posthook – Job Scheduling as a Service

#23

Post by throwaway2016a »

hayd wrote: post #14

I use cloudwatch events, you can configure cron/frequency and define json to send out.

We use CloudWatch events too. It works really well but does require a bit more technical know-how and debugging than a simple cURL so there is that.

Re: Show HN: Posthook – Job Scheduling as a Service

#24

Post by cgenuity »

sebringj wrote: post #12

This is a good niche with the rise of serverless as there isn't a super simple way to do this if you want to hit some job every so often. You could set a header key that all requests require and bam, you got security for an ongoing task. I use kue.js myself with jobs for node and glue stuff together with redis across servers but serverless seems like it could work for a lot of use cases coupled with this idea with le…

Thanks sebringj! I agree and the rise of serverless was definitely one of the motivating factors to me building this service. Security is handled through signing the payload that includes a timestamp with an HMAC to prevent replay attacks as well.

Re: Show HN: Posthook – Job Scheduling as a Service

#25

Post by cgenuity »

nodesocket wrote: post #15
cgenuity wrote: post #9

Earlier quoted context omitted.

It does not support recurring scheduling at the moment. Right now the retry logic is just one retry 5 seconds after the first failure. At which point the hook gets set to a failed status and failure notifications get sent out. Retries are tricky because depending on how the job is implemented they can cause more harm than good. So I plan to refine that more based on customer feedback.

Seems like allowing the user to specify retry logic (if any) covers the "tricky" pieces. Let the user define the number of retries and delay between.

Agreed, thank you :). Added to the board.

Re: Show HN: Posthook – Job Scheduling as a Service

#26

Post by TomMarius »

paddy_m wrote: post #16

I would be really interested in a distributed job running system with a scheduler. I want a UI where I can set jobs via a schedule that run on one of many workers. In that same UI I want to be able to look at failed jobs and see all of the output from that job. I don't want to have to ssh over to the box where the job ran to retrieve a log file. I once had a job where we used Tidal Enterprise Scheduler which poorly i…

Would you pay for this? How much and what pricing scheme would you prefer?

Re: Show HN: Posthook – Job Scheduling as a Service

#27

Post by rglover »

cgenuity wrote: post #2

Hello all! I built Posthook as a simple solution for web applications to schedule one-off tasks. It lets you schedule a request back to your application for a certain time, with an optional JSON payload. It can be an alternative to running your own systems like Sidekiq, Celery, or Quartz and the operational overhead that comes along with them. Cron jobs and cloud provider tools like CloudWatch Events are also used fo…

Thank you for this. I've been on the hunt for this exact service for awhile now but a lot of the options were lacking. Excited to give this a try.

Re: Show HN: Posthook – Job Scheduling as a Service

#28

Post by xorcist »

paddy_m wrote: post #16

I would be really interested in a distributed job running system with a scheduler. I want a UI where I can set jobs via a schedule that run on one of many workers. In that same UI I want to be able to look at failed jobs and see all of the output from that job. I don't want to have to ssh over to the box where the job ran to retrieve a log file. I once had a job where we used Tidal Enterprise Scheduler which poorly i…

Rundeck does exactly this.

If you already have something like Jenkins you could probably bend that to your will, too.

Post reply on HN