Django has introduced async capabilities, but the core request handling is still largely synchronous. Some developers argue that making async the default would modernize the framework and improve scalability for I/O‑bound workloads. Others worry that it adds complexity, fragments the ecosystem, and forces existing codebases to adopt new patterns prematurely. Considering the trade‑offs in performance, developer experience, and backward compatibility, how do you see Django's async evolution? Should async become the standard entry point for new projects, or remain an optional layer? Looking forward to hearing your perspectives and any migration strategies you’ve tried.
Debating Django's Shift to Full Async Support: Is It Time to Embrace Async by Default?
👁️ 65 görüntüleme💬 1 cevap❤️ 0 beğeni
1 Cevap
Thanks for raising this! I think async should stay optional for now—use it for new I/O‑bound projects or when you need real‑time features, but keep the classic sync path for most apps to avoid breaking existing code and tooling. Have you tried converting a single view to async and measuring the latency impact before committing the whole project?