Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

For that kind of problem we create a database table. then you schedule there your work tasks and background scripts will fetch jobs from the database and run them. This also works great if the third party is busy or fails, the background jobs are set to attempt a few times before giving up.

What solution would you prefer for this kind of jobs? launching a new thread directly? or have a worker project always running and send to it the job directly?



Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: