Show HN: Posthook – Job Scheduling as a Service
1–10 of 76 posts
Re: Show HN: Posthook – Job Scheduling as a Service
#2Hello 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 for job scheduling but lack observability and may force you to frequently make expensive queries to your data store just to see if there is any work to do.
Questions and feedback are greatly appreciated :)
Re: Show HN: Posthook – Job Scheduling as a Service
#3Hello 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…
I'm unclear about the part about expensive queries to the data store. What cron/celery/quartz job would require a check to the data store for a check that wouldn't need to be done with posthook? It seems like if work depends on a decision made with data from my data store, that doesn't change based on what I use as a timer for the task. I'm not sure that I see a clear value-add here.
Re: Show HN: Posthook – Job Scheduling as a Service
#4Hello 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…
I'm unclear about the part about expensive queries to the data store. What cron/celery/quartz job would require a check to the data store for a check that wouldn't need to be done with posthook? It seems like if work depends on a decision made with data from my data store, that doesn't change based on what I use as a timer for the task. I'm not sure that I see a clear value-add here.
With a recurring job say every minute, the query triggered by the job to send out event reminders would be something like "get me all the events starting in one hour." With Posthook, you are able to start jobs only when needed and the query changes to something like "do I still need to send out a reminder for this event id."
Re: Show HN: Posthook – Job Scheduling as a Service
#5Hello 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…
Hey cgenuity,
Great to see the simplicity, I am working on a very similar product, launched couple of days back on HN (https://send.rest). Best of luck.
But have added couple of extra features in send.rest
1) Calling external APIs ( Think : pull data from Facebook while running this task in future and post data on my API or send SMS )
2) Reports and retries ( Try 3 times or send me sms its failing )
3) Recurrence ( Call this task every Monday 9:00 pm )
4) SMS and Emails comes along with them ( Send SMS or Email , pick any service as your backend )
I guess without some extra features it will be difficult to get a market acceptance.
Re: Show HN: Posthook – Job Scheduling as a Service
#6Hello 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…
Does Posthook support recurring scheduling (i.e. every 15 minutes)?
Also, is there retry logic? I.E. 3 retries, delay 60 seconds between retries?
Re: Show HN: Posthook – Job Scheduling as a Service
#7Hello 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…
Hey cgenuity, Great to see the simplicity, I am working on a very similar product, launched couple of days back on HN ( https://send.rest ). Best of luck. But have added couple of extra features in send.rest 1) Calling external APIs ( Think : pull data from Facebook while running this task in future and post data on my API or send SMS ) 2) Reports and retries ( Try 3 times or send me sms its failing ) 3) Recurrence (…
Thank you, good luck to you as well!
I've found that with scheduling tasks for the future it's important to do a final check before fulfilling the action, whether it's sending an email, push notification, etc. You don't want to send a reminder for an event that has been deleted, for example. That is why I have decided to keep the scope small and let developers make the final decision there.
Reports and retries are definitely things that I think add value though, and I have plans to expand on that.
Re: Show HN: Posthook – Job Scheduling as a Service
#8Earlier quoted context omitted.
Hey cgenuity, Great to see the simplicity, I am working on a very similar product, launched couple of days back on HN ( https://send.rest ). Best of luck. But have added couple of extra features in send.rest 1) Calling external APIs ( Think : pull data from Facebook while running this task in future and post data on my API or send SMS ) 2) Reports and retries ( Try 3 times or send me sms its failing ) 3) Recurrence (…
Thank you, good luck to you as well! I've found that with scheduling tasks for the future it's important to do a final check before fulfilling the action, whether it's sending an email, push notification, etc. You don't want to send a reminder for an event that has been deleted, for example. That is why I have decided to keep the scope small and let developers make the final decision there. Reports and retries are de…
I also think there might be a market for this kind of product .. Great to see more people think on the same line .. Got some paid signups from last week also ..
You might be right about email/push, but it certainly comes handy if minimal config is required.
Re: Show HN: Posthook – Job Scheduling as a Service
#9Hello 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…
Does Posthook support recurring scheduling (i.e. every 15 minutes)? Also, is there retry logic? I.E. 3 retries, delay 60 seconds between retries?
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.
Re: Show HN: Posthook – Job Scheduling as a Service
#10Earlier quoted context omitted.
Does Posthook support recurring scheduling (i.e. every 15 minutes)? Also, is there retry logic? I.E. 3 retries, delay 60 seconds between retries?
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.
What happens when you have a service outage? Do you directly mark the hooks as failed, or do you retry once after your service has been restored?