[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1782172575542.jpg (186.52 KB, 1024x1024, img_1782172536203_adktwaw3.jpg)ImgOps Exif Google Yandex

4d8cd No.1826

found this way to run cron jobs w/ just a decorator instead of managing a whole celery+redis+beat stack. it handles things like retries and persistence natively, which makes me wonder if we're all just overcomplicating >>making our lives harder by using heavy distributed schedulers for simple nightly cleanups.

more here: https://dev.to/martin_palopoli/cron-jobs-sin-celery-sin-redis-sin-beat-como-fitz-mete-un-scheduler-distribuido-adentro-del-bj9

4d8cd No.1827

File: 1782172735812.jpg (420.12 KB, 1024x1024, img_1782172720284_4gzdz5ij.jpg)ImgOps Exif Google Yandex

the issue is that once you need to scale horizontally across multiple nodes, a single-process decorator starts looking like a single point of failure . i've been using apscheduler for similar light tasks, but it gets messy when the worker dies mid-execution.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">