←back to thread

Django 6.0 beta 1 released

(www.djangoproject.com)
106 points webology | 1 comments | 22 Oct 25 19:46 UTC | HN request time: 0.215s | source
Show context
tkcranny ◴[22 Oct 25 20:23 UTC] No.45674677[source]▶
Looks like Django 6 is getting an offical task system.

There’s no real world brokers or workers supported (at least built in), but still centralising around a standard interface might make things nicer than the celery tentacle monsters Django apps eventually tend to mutate into.

replies(3): >>45674764 #>>45675195 #>>45675539 #
gdulli ◴[22 Oct 25 21:43 UTC] No.45675539[source]▶
Right, I'd never touch celery, but RQ is simple and has never let me down.
replies(1): >>45676271 #
scorpioxy ◴[22 Oct 25 23:04 UTC] No.45676271[source]▶
I'm curious, why is that? I've heard that sentence before but usually from people who want to write their own task system and end up partially implementing what celery implements just worse.

Celery is large and complex now and edge cases always show up at scale but that is usually not a reflection of the platform quality. The custom implementations I've seen are no where near what celery is capable of and can cater to so haven't seen the edge cases yet but that doesn't mean they implemented bug-free code and celery hasn't.

After asking about it, the issue always went towards a hand-wavey "performance". What is your experience on that front?

replies(2): >>45676363 #>>45676874 #
1. pmontra ◴[22 Oct 25 23:16 UTC] No.45676363[source]▶
My experience is that Celery is fragile. It loses the connection with RabbitMQ sometimes and it needs a restart to recover. I never had those problems with Rails and Sidekiq + Redis.