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 do I integrate my git PHP repo into an official Docker Hub container?
  • docker swarm access service
  • Capturing output of python script run inside a docker container
  • “tput: No value for $TERM and no -T specified ” error on docker [on hold]
  • Files created inside docker are write protected on host
  • Building Dockerfile fails when touching a file after a mkdir
  • Docker-Machine and Swarm behind proxy
  • Udeploy not projecting the data
  • Docker on windows: data in mounted volume doesn't updated
  • Docker for Windows 10 //./pipe/docker_engine: access is denied
  • How can I make a host directory mount with the container directory's contents?
  • How can I expose kubernetes services running within docker?
  • 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.