Uvicorn and nginx are two completely different things in your web stack. For production, you typically don’t expose Uvicorn directly to the public. Instead, nginx receives all traffic, serves static assets efficiently, and forwards dynamic requests to Uvicorn. Uvicorn’s website explains each components role in your stack: “Using Nginx as a proxy in front of your Uvicorn processes may not be necessary, but is recommended for additional resilience. Nginx can deal with serving your static media and buffering slow requests, leaving your application servers free from load as much as possible. In managed environments such as Heroku, you won’t typically need to configure Nginx, as your server processes will already be running behind load balancing proxies.”

The question is not “What’s the difference between running uvicorn vs nginx?” But “When should I use Nginx to deploy with Uvicorn?” Hope this makes sense.

Much appreciated guys!

Thanks everyone for their interest in this little project. We removed the drawing and any evenn somewhat Disney references. Disney does not own ‘kenobi’, they do own ‘Obi-Wan Kenobi’ and ‘Ben Kenobi’. There is nothing to do with either of these names of the Star Wars character on the github or pypi now. Thanks for the feedback everyone!