Docker replicas vs gunicorn workers in production

Do we need gunicorn or uwsgi workers when we have docker replicas? What is the best solution, make guincorn worker and replicate it on docker, or make multiple gunicorn workers?

  • How to launch a new docker container from inside a docker container on openshift
  • Can't access Docker images when using user namespace
  • Why am I unable to access my node.js app within a docker container?
  • How do I mount --bind inside a Docker container?
  • Localhost connect MySQL Docker confusion
  • Sending build context to Docker daemon (it doesn't stop)
  • Answer '29' to apt-get install prompt for xorg
  • Docker for Windows 10 //./pipe/docker_engine: access is denied
  • Why does docker compose exit right after starting?
  • Connect to a VNC inside a docker which is on remote server
  • Packer Docker builder using chmod on Windows 10
  • Airbnb Airflow using all system resources
  • One Solution collect form web for “Docker replicas vs gunicorn workers in production”

    Based on kubernetes philosophy of Deployments, I believe you can mix up both approaches.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.