What is the difference between WSGI and ASGI, and when do you need ASGI for a Django project? WSGI और ASGI में क्या अंतर है, और Django प्रोजेक्ट के लिए ASGI की ज़रूरत कब पड़ती है?

WSGI (Web Server Gateway Interface) is the traditional synchronous interface between a Python web application and its server: one worker handles one request at a time, blocking until it completes, which is simple and battle-tested for standard request/response HTTP apps. ASGI (Asynchronous Server Gateway Interface) is its successor, supporting asynchronous request handling, long-lived connections, and protocols beyond plain HTTP.

ASGI is required specifically when a Django project uses Django Channels for WebSockets or other persistent connections (live chat, real-time notifications, live dashboards), or when using async views/middleware to concurrently fan out to multiple external services. A typical CRUD-only Django app with no real-time features has no strong need for ASGI and can stay on WSGI with Gunicorn.

application = ProtocolTypeRouter({
    "http": django_asgi_app,
    "websocket": AuthMiddlewareStack(URLRouter(chat.routing.websocket_urlpatterns)),
})