Skip to content
This repository has been archived by the owner on Nov 26, 2022. It is now read-only.

Celery is a liability #398

Open
codl opened this issue Feb 7, 2021 · 0 comments
Open

Celery is a liability #398

codl opened this issue Feb 7, 2021 · 0 comments

Comments

@codl
Copy link
Owner

codl commented Feb 7, 2021

Celery + beat continue to bite me in the butt whenever I stop looking at them, I don't think this "queue worker + queue scheduler pushing tasks at a steady rate" is healthy. Maybe it is time to change.

There are a couple of other queue systems in python but as far as I remember, they don't try to solve this particular problem.

Maybe a queue system is not the correct paradigm, as there are very few heavy jobs that are actually initiated by the user and need queueing:

  • A couple things that happen on log in
  • Twitter archives (haha rip)

Everything else just needs to happen on a schedule.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant