Show HN: Posthook – Job Scheduling as a Service

Re:Show HN: Posthook – Job Scheduling as a Service by cgenuity on Tuesday June 19, 2018 @04:19PM (#17349979)

I understand Posthook may not be the best solution for everyone's scheduled tasks. It seems like for that project you had the expertise, time, and risk tolerance to set up that one DO server to handle all your needs. Other developers may be in a different situation and may find Posthook useful.

> How much would it cost to do 3 million requests per month?

If you want to use Posthook to schedule 3 million requests a month please email support [at] posthook.io and we can work out a special plan and support contract. Do keep in mind that background jobs and scheduled jobs are two different things and what I aim for Posthook to solve are scheduled jobs. I suspect a big part of those 3 million were background jobs.

> Also how would you set up custom retry policies?

The retry policy is fixed at the moment but it seems like this a common request so I want to roll that feature out soon.

[ Parent | on HN ]

Re:Show HN: Posthook – Job Scheduling as a Service by nickjj on Tuesday June 19, 2018 @07:29PM (#17351143)

> I suspect a big part of those 3 million were background jobs.

Yep, almost all of them were tasks that should be executed as soon as possible, but Celery also allows for you to schedule tasks at a future date, and deal with running scheduled tasks at a repeated time (every Sunday at 3am, etc.).

As for the price, I was just curious for the sake of wanting to compare it to the $20 / month DO set up.

Thanks for the answers.

[ Parent | on HN ]

Re:Show HN: Posthook – Job Scheduling as a Service by wrs on Tuesday June 19, 2018 @05:00PM (#17350259)

Once you have a retry policy, you pretty much by definition have scheduled jobs, so just slap an API on there and you’re all set. (jk)

[ Parent | on HN ]