←back to thread

Django: what’s new in 6.0

(adamj.eu)
378 points rbanffy | 1 comments | 09 Dec 25 20:33 UTC | HN request time: 1.28s | 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. leobuskin ◴[10 Dec 25 02:11 UTC] No.46213237[source]▶
It's okay till it's not. Everyone I know who had Celery in production was looking for a substitution (custom or third-party) on a regular basis. Too many moving pieces and nuances (config × logic × backend), too many unresolved problems deep in its core (we've seen some ghosts you can't debug), too much of a codebase to understand or hack. At some point we were able to stabilize it (a bunch of magic tricks and patches) and froze every related piece; it worked well under pressure (thanks, RabbitMQ).