5 ms·

Show HN: Cronit – Online Cronjobs

16 points by aclarembeau 4y ago

zoover2020 4y ago
I think you can improve the landing page, I have no idea how long the job timeout is and "Limited" vs "Full" features is way too ambigiuous.
- blacksoil 4y ago
  Yeah I second this. Also to try one would need to login, which I think would make a lot of people leave before knowing what the product is about
  - aclarembeau 4y ago
    Thanks for the feedback. Could you tell me what kind of information do you think is missing?
unsignednoop 4y ago
Fyi: the cron.it domain appears to be available
- radiojasper 4y ago
  No, sorry. Been registered since 1999-06-29.
  - aclarembeau 4y ago
    Thanks for the heads up. Anyway, I think .app is good for a moment
Upitor 4y ago
peter_d_sherman 4y ago
What a brilliant, yet simple, yet brilliant idea! Observation: Online cron jobs are not unlike online containerized web services (both involve running code) -- the difference is in the invocation event -- online web services are typically invoked in response to an HTTP (or other protocol) request, online cron jobs are invoked in response to a timer event, that is, in response to a specific, pre-scheduled, time. So we have both request-based and pre-scheduled time-slot based -- invocation methods... In theory there could be online code invocation -- based on a series of user-defined events and/or conditions... sort of like "if the time is X" and "the temperature in Siam is 52 degrees" and "Our shipping partner in the far east has just shipped 50,000 widgets" -- then send them an email... or invoke some code which does something like that... Or perhaps, a connected web search just returned a new web page containing specific search terms -- now run some code to process that page in some way, and return the results formatted to some format... The possibilities are endless... Observation: There's not just code that lives online -- but there are all sorts of conditions, other than http requests and pre-scheduled time slots -- that could cause code to be invoked, for one reason or another... Perhaps there's a future business for creating a control panel for users to invoke their online code -- in response to different types of events/sets of conditions -- occuring in the real and/or digital world... Anyway, once again, great idea for online cron jobs -- and I wish you all of the success in the world with your business!
- killingtime74 4y ago
  Have you not just described AWS Lambda and other similar serverless offerings?
  - tedmiston 4y ago
    Exactly. This is why we have CloudWatch Events (now called EventBridge). https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/WhatIsCloudWatchEvents.html https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/W... https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-...
    - 4y ago

16 points by aclarembeau 4y ago

zoover2020 4y ago

I think you can improve the landing page, I have no idea how long the job timeout is and "Limited" vs "Full" features is way too ambigiuous.

blacksoil 4y ago
Yeah I second this. Also to try one would need to login, which I think would make a lot of people leave before knowing what the product is about
- aclarembeau 4y ago
  Thanks for the feedback. Could you tell me what kind of information do you think is missing?

unsignednoop 4y ago

Fyi: the cron.it domain appears to be available

radiojasper 4y ago
No, sorry. Been registered since 1999-06-29.
- aclarembeau 4y ago
  Thanks for the heads up. Anyway, I think .app is good for a moment

Upitor 4y ago

peter_d_sherman 4y ago

What a brilliant, yet simple, yet brilliant idea! Observation: Online cron jobs are not unlike online containerized web services (both involve running code) -- the difference is in the invocation event -- online web services are typically invoked in response to an HTTP (or other protocol) request, online cron jobs are invoked in response to a timer event, that is, in response to a specific, pre-scheduled, time. So we have both request-based and pre-scheduled time-slot based -- invocation methods... In theory there could be online code invocation -- based on a series of user-defined events and/or conditions... sort of like "if the time is X" and "the temperature in Siam is 52 degrees" and "Our shipping partner in the far east has just shipped 50,000 widgets" -- then send them an email... or invoke some code which does something like that... Or perhaps, a connected web search just returned a new web page containing specific search terms -- now run some code to process that page in some way, and return the results formatted to some format... The possibilities are endless... Observation: There's not just code that lives online -- but there are all sorts of conditions, other than http requests and pre-scheduled time slots -- that could cause code to be invoked, for one reason or another... Perhaps there's a future business for creating a control panel for users to invoke their online code -- in response to different types of events/sets of conditions -- occuring in the real and/or digital world... Anyway, once again, great idea for online cron jobs -- and I wish you all of the success in the world with your business!

killingtime74 4y ago
Have you not just described AWS Lambda and other similar serverless offerings?
- tedmiston 4y ago
  Exactly. This is why we have CloudWatch Events (now called EventBridge). https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/WhatIsCloudWatchEvents.html https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/W... https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-...
  - 4y ago