←back to thread

Django: what’s new in 6.0

(adamj.eu)
378 points rbanffy | 4 comments | 09 Dec 25 20:33 UTC | HN request time: 1.289s | source
Show context
teagee ◴[09 Dec 25 21:37 UTC] No.46211038[source]▶
Any code or blog written by Adam is worth spending some time on.

It will be interesting to see how the tasks framework develops and expands. I am sad to see the great Django-Q2 lumped in with the awful Celery though.

replies(9): >>46211810 #>>46212076 #>>46212142 #>>46212219 #>>46212861 #>>46215681 #>>46215766 #>>46216187 #>>46217127 #
hintoftime ◴[09 Dec 25 23:19 UTC] No.46212076[source]▶
Why is celery awful?
replies(4): >>46212860 #>>46213125 #>>46213237 #>>46213833 #
1. JimDabell ◴[10 Dec 25 03:45 UTC] No.46213833[source]▶
> The Many Problems with Celery:

— https://steve.dignam.xyz/2023/05/20/many-problems-with-celer...

> The problems with (Python’s) Celery:

— https://docs.hatchet.run/blog/problems-with-celery

> Dramatiq motivation:

— https://dramatiq.io/motivation.html

Here are some alternatives:

Dramatiq: https://github.com/Bogdanp/dramatiq

RQ: https://github.com/rq/rq

Huey: https://github.com/coleifer/huey

Hatchet: https://github.com/hatchet-dev/hatchet

replies(2): >>46215456 #>>46216788 #
2. hda111 ◴[10 Dec 25 08:37 UTC] No.46215456[source]▶
django-q2: https://github.com/django-q2/django-q2
3. hintoftime ◴[10 Dec 25 12:03 UTC] No.46216788[source]▶
Would you consider tools like Temporal, DBOS, Absurd Workflows, PGQueuer as alternatives?

https://temporal.io/

https://docs.dbos.dev/

https://news.ycombinator.com/item?id=45797228

https://python-absurd-client.readthedocs.io/en/latest/quicks...

https://pgqueuer.readthedocs.io/en/latest/

replies(1): >>46218956 #
4. meesles ◴[10 Dec 25 15:40 UTC] No.46218956[source]▶
Temporal is an AMAZING piece of software, however I don't believe it's a replacement for something more simple like Celery. Even if you write helpers, the overhead to setting up workflows, invoking them, etc. is just too much for simple jobs like sending an email (imo). I would love to work in a codebase that had access to both, depending on the complexity of what you're trying to background.