Gunicorn fundamentally runs everything as a worker process. You have sync, gthread, gevent, evenlet, tornado (tornado was also a popular server). UvicornWorker

Gunicorn fundamentally runs everything as a worker process. You have sync, gthread, gevent, evenlet, tornado (tornado was also a popular server). UvicornWorker is another type of gunicorn worker... incidentally authored by the same guys who built uvicorn. Nothing strange at all. But ur question is genuine - but it is orthogonal to the uvicorn part of this answer. Fundamentally, in a k8s model...why bother with gunicorn? The answer: I don't know. I do love the control that gunicorn gives me...so I'd probably use it even if I was using a single worker. However there is a complex answer with Threads vs cores vs pods that I'm unqualified to give.