<p>This is going to be an opinionated answer as both options are clearly possible.</p>

<p>I would go with the first option you described for the following reason:</p>

<p>It seems that at the moment you don't have a lot of microservices (otherwise you wouldn't be using docker-compose and would likely be doing k8s or at least docker swarm). Now, if your application grows a lot - you would likely outgrow compose in any case, so it would be wasteful if you optimize for compose at this stage anticipating future complexity.</p>

<p>So my take would be to go with option 1 for now which is much easier to implement. And when you need extra flexibility, likely you'd have other reasons to switch from docker-compose to something else.</p>

CC BY-SA 4.0
2020-03-11T10:49:06.447Z
Thank you very much for the reply, @taleodor. And the case of using networks, when would it be more advisable? If you want to use docker-compose (an assumption) to deploy multiple microservices, wouldn't the second option be better? Using the first one would be difficult to handle, in my opinion.
Mr. Mars
CC BY-SA 4.0
2020-03-11T23:31:18.107Z
@Mr.Mars As I mentioned in the answer, I'd say if you find yourself in the situation where using networks is beneficial - you might as well migrate your stack to k8s and it would likely be most reasonable thing to do.
Where you would may use networks in compose - is if you have Docker Swarm cluster and you're testing it on compose. Other than that I don't see real use case nowadays.
taleodor
CC BY-SA 4.0
2020-03-11T02:51:12.457Z
2020-03-11T23:28:44.103Z
2020-03-11T23:28:44.103Z
taleodor
<p>Having the following architecture:</p>

<ul>
<li>Microservice 1 + DB (microservice1/docker-compose.yml)</li>
<li>Microservice 2 + DB (microservice2/docker-compose.yml)</li>
<li>Proxy (proxy/docker-compose.yml)</li>
</ul>

<p>Which of the following options would be the best to deploy in the production environment?</p>

<ol>
<li>Docker Compose Overriding. Have a docker-compose for each microservice and another docker-compose for the proxy. When the production deployment is done, all the docker-compose would be merged to create only one (with <code>docker-compose -f microservice1/docker-compose.yml -f microservice2/docker-compose.yml -f proxy/docker-compose.yml up</code>. In this way, the proxy container, for example nginx, would have access to microservices to be able to redirect to one or the other depending on the request.</li>
<li>Shared external network. Have a docker-compose for each microservice and another docker-compose for the proxy. First, an external network would have to be created to link the proxy container with microservices.<code>docker network create nginx_network</code>. Then, in each docker-compose file, this network should be referenced in the necessary containers so that the proxy has visibility of the microservices and thus be able to use them in the configuration. An example is in the following link <a href="https://stackoverflow.com/a/48081535/6112286">https://stackoverflow.com/a/48081535/6112286</a>.</li>
</ol>

<p>The first option is simple, but offers little felxibility when configuring many microservices or applications, since all docker-compose of all applications would need to be merged to generate the final configuration. The second option uses networks, which are a fundamental pillar of Docker. On the other hand, you don't need all docker-compose to be merged.</p>

<p>Of these two options, given the scenario of having several microservices and needing a single proxy to configure access, which would be the best? Why?</p>

<p>Tnahks in advance.</p>

<docker><docker-compose><dockerfile>
Multiple apps (microservices) and one proxy (nginx) docker-compose configuration/architecture
Mr. Mars
# Multiple apps (microservices) and one proxy (nginx) docker-compose configuration/architecture

(Asked by: username_0 on 2020-03-10)

Having the following architecture:

* Microservice 1 + DB (microservice1/docker-compose.yml)
* Microservice 2 + DB (microservice2/docker-compose.yml)
* Proxy (proxy/docker-compose.yml)

Which of the following options would be the best to deploy in the production environment?

1. Docker Compose Overriding. Have a docker-compose for each microservice and another docker-compose for the proxy. When the production deployment is done, all the docker-compose would be merged to create only one (with `docker-compose -f microservice1/docker-compose.yml -f microservice2/docker-compose.yml -f proxy/docker-compose.yml up`. In this way, the proxy container, for example nginx, would have access to microservices to be able to redirect to one or the other depending on the request.
2. Shared external network. Have a docker-compose for each microservice and another docker-compose for the proxy. First, an external network would have to be created to link the proxy container with microservices.`docker network create nginx_network`. Then, in each docker-compose file, this network should be referenced in the necessary containers so that the proxy has visibility of the microservices and thus be able to use them in the configuration. An example is in the following link <https://stackoverflow.com/a/48081535/6112286>.

The first option is simple, but offers little felxibility when configuring many microservices or applications, since all docker-compose of all applications would need to be merged to generate the final configuration. The second option uses networks, which are a fundamental pillar of Docker. On the other hand, you don't need all docker-compose to be merged.

Of these two options, given the scenario of having several microservices and needing a single proxy to configure access, which would be the best? Why?

Tnahks in advance.

**Tags:** docker, docker-compose, dockerfile


---

## 1 answers

### Answer by username_1 on 2020-03-11. Score: 4 | Accepted answer

This is going to be an opinionated answer as both options are clearly possible.

I would go with the first option you described for the following reason:

It seems that at the moment you don't have a lot of microservices (otherwise you wouldn't be using docker-compose and would likely be doing k8s or at least docker swarm). Now, if your application grows a lot - you would likely outgrow compose in any case, so it would be wasteful if you optimize for compose at this stage anticipating future complexity.

So my take would be to go with option 1 for now which is much easier to implement. And when you need extra flexibility, likely you'd have other reasons to switch from docker-compose to something else.

> **Comments:**
> **username_0**: Thank you very much for the reply, @username_1. And the case of using networks, when would it be more advisable? If you want to use docker-compose (an assumption) to deploy multiple microservices, wouldn't the second option be better? Using the first one would be difficult to handle, in my opinion.  
> **username_1**: @Mr.Mars As I mentioned in the answer, I'd say if you find yourself in the situation where using networks is beneficial - you might as well migrate your stack to k8s and it would likely be most reasonable thing to do. Where you would may use networks in compose - is if you have Docker Swarm cluster and you're testing it on compose. Other than that I don't see real use case nowadays.  

---

