Why You Should (Almost) Always Choose Sync Gunicorn Workers

Data Science Tech Brief By HackerNoon

This story was originally published on HackerNoon at: https://hackernoon.com/why-you-should-almost-always-choose-sync-gunicorn-over-workers-ze9c32wj.
Anyone working on a WSGI web application frameworks like Flask would know that as a best practice it is very important to use a WSGI HTTP Server like Gunicorn to deploy the app outside your development servers.
Check more stories related to data-science at: https://hackernoon.com/c/data-science. You can also check exclusive content about #python-programming, #gevent, #gunicorn, #python-web-development, #flask, #flask-deployment, #latest-tech-stories, #what-are-gunicorn-worker-types, and more.
This story was written by: @shamik-ray. Learn more about this writer by checking @shamik-ray's about page, and for more stories, please visit hackernoon.com.
Gunicorn is a widely popular WSGI Server and its popularity is because it is lightweight, fast, simple yet can support most of the requirements you would have to host an app on production. The default worker type is Sync and I will be arguing for it. Async workers like Gevent create new greenlets (lightweight pseudo threads) Every time a new request comes they are handled by greenlets spawned by the worker threads. At the same time, the resources needed to serve the requests will be less.