Django Developers Scrutinize Celery's Limits: A New Async Task Queue Poised to Disrupt Django Stacks
The conversation centers on modernizing asynchronous task queuing within Django, specifically comparing existing tools like Celery against a new solution, django-vtasks.
The core argument revolves around performance and true asynchronous capability. The developer 'bufke' introduced 'django-vtasks' for the GlitchTip project, arguing it offers superior concurrency and better performance benchmarks against Celery. The central selling point is its ability to enable native asyncio calls, bypassing the limitations of synchronous wrappers like `sync_to_async`.
'bufke' explicitly stated that 'django-tasks' fell short for high-concurrency needs. The underlying tension is clear: the industry needs a Django task queue that fully embraces modern Python concurrency paradigms, and the community is assessing whether 'django-vtasks' delivers on that high-performance, asyncio-first promise.
Key Points
django-vtasks aims to replace Celery for Django background tasks.
bufke developed it for GlitchTip, citing performance necessity.
The system must support true asyncio operations.
The key advantage cited is avoiding reliance on `sync_to_async` wrappers for operations like connecting to Valkey.
django-vtasks supports multiple backends.
The tool supports both Valkey and Postgres backends, alongside performance claims.
Existing solutions like 'django-tasks' are inadequate.
bufke noted that 'django-tasks' was not performant enough for their high concurrency requirement.
Source Discussions (4)
This report was synthesized from the following Lemmy discussions, ranked by community score.