Using Nginx as micro service API gateway

We are splitting our monolith API into micro services.

We do not need rate-limiting, auth, caching or any other gateway like abilities.

  • How to use docker-compose on ovh hosting
  • Nodemon Docker ECONNREFUSED error
  • Running multiple time the same docker image
  • How do I run a docker swarm node on the same machine as the swarm manager?
  • Two WordPress Containers on Kitematic
  • How to open 3000 port on Amazon EC2 for Docker Container?
  • Would it be a valid approach to use very simple stateless Nginx containers that route to the underlying services?

  • Confluent Platform : Update Schema Registry to use Avro 1.8.1 and use new build in docker and host
  • Rocket.Chat as Docker-Container using sub folder
  • Using docker for unit test
  • GitLab-CI multi runner start docker container
  • Dockerfile custom commands/directives
  • Is any way to Openshift respect Docker ENV variables
  • 2 Solutions collect form web for “Using Nginx as micro service API gateway”

    Yes, Nginx can be a deployment and a service (of loadbalancer or externalIP type) and can forward to upstream services.

    You might have to frequently change the nginx.conf though (when you add/remove services), so I would recommend using a ConfigMap to keep your nginx.conf and mounting that as a volume in your deployment. Refer: http://kubernetes.io/docs/user-guide/configmap/ and scroll down to consume configmap via volumes.

    Another thing to keep in mind is that if you delete and create a service that is referred to in nginx.conf as an upstream service, you’ll have to restart your deployment because nginx resolves all service DNS labels when nginx starts.

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