←back to thread

528 points sealeck | 1 comments | | HN request time: 0.217s | source
Show context
st3fan ◴[] No.31391017[source]
For me the missing bit in Fly is scheduled tasks. I know how to solve this by spinning up an app that runs permanently as a scheduler, but basic cron-like scheduling should be part of the platform IMO. All other FaaS-like service do this.
replies(1): >>31391035 #
tptacek ◴[] No.31391035[source]
I'd love to do this, if for no other reason than I hate working with cron. What would you use it for? What would the ideal version of this feature look like for you? What kind of apps would you be more easily able to ship? Is it mostly so you wouldn't need to keep a single tiny running VM sitting around running cron?
replies(4): >>31391264 #>>31391274 #>>31391522 #>>31391997 #
joseph ◴[] No.31391997[source]
I'd like to do any one-off job, not only scheduled ones; retrieving data and transforming or storing it, scraping a web page, running a database migration. My biggest annoyance with Fly is the assumption that everything is a long running application.
replies(2): >>31392211 #>>31393036 #
1. kevlened ◴[] No.31393036[source]
I'm not sure how Fly handles one-off tasks behind the scenes, but we're building task queues (w/ cron) as a first class citizen at https://tasker.sh