What is Gunicorn?
Who uses Gunicorn?
Why developers like Gunicorn?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Gunicorn in their tech stack.
Unlike our frontend, we chose Flask, a microframework, for our backend. We use it with Python 3 and Gunicorn.
One of the reasons was that I have significant experience with this framework. However, it also was a rather straightforward choice given that our backend almost only serves REST APIs, and that most of the work is talking to the database with SQLAlchemy .
We could have gone with something like Hug but it is kind of early. We might revisit that decision for new services later on.
I use Gunicorn because does one thing - it’s a WSGI HTTP server - and it does it well. Deploy it quickly and easily, and let the rest of your stack do what the rest of your stack does well, wherever that may be.
uWSGI “aims at developing a full stack for building hosting services” - if that’s a thing you need then ok, but I like the principle of doing one thing well, and I deploy to platforms like Heroku and AWS Elastic Beanstalk where the rest of the “hosting service” is provided and managed for me.
Gunicorn is WSGI container that we used to run our Tornado code as it supports Asynchronous operations on tornado. Gunicorn
Gunicorn runs as the HTTP application server. Serves the django application in WSGI mode. Gunicorn