Answer the question
In order to leave comments, you need to log in
How to deploy N microservices from different repositories using docker-compose?
Hey!
I went around a lot of articles, reviewed a lot of conferences, and so far there is no understanding of how to most correctly deploy a microservice infrastructure.
So, what we have:
- N microservices, some of which communicate with each other via HTTP
- N repositories equal to the number of microservices
- Nginx as a proxy server
- Ordinary services in the form of redis or mysql behind + several admin panels
- docker-compose in combat and test environments for orchestration (so far)
- A huge and heavy repository with a bunch of configs, which is responsible for the deployment process of each microservice (in my opinion, it is illogical)
Question: Can it be simplified? Are there any good practices for orchestrating microservices on remote hosts with docker-compose? How to make sure that each repository (microservice) is responsible only for itself, but in the end it is part of the same infrastructure?
Thank you!
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question