←back to thread

Fly.io: The reclaimer of Heroku's magic

(christine.website)
528 points sealeck | 2 comments | 15 May 22 19:56 UTC | HN request time: 0s | source
Show context
st3fan ◴[15 May 22 20:53 UTC] 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 ◴[15 May 22 20:56 UTC] 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 #
krn ◴[15 May 22 21:53 UTC] No.31391522[source]▶
> What would the ideal version of this feature look like for you?

I think that Render solved "Cron as a Service" beautifully:

https://render.com/docs/cronjobs

replies(1): >>31392311 #
1. st3fan ◴[15 May 22 23:44 UTC] No.31392311{3}[source]▶
I would use render but fly.io persistent storage is a killer feature. It is literally 100x simpler to just deal with files on a real file system than having to deal with remote object storage.
replies(1): >>31392334 #
2. anurag ◴[15 May 22 23:48 UTC] No.31392334[source]▶
Render has persistent disks! https://render.com/docs/disks. We need to expose them for cron jobs though.