Answer the question
In order to leave comments, you need to log in
How do you feel about the fact that the entire site architecture in production is “packed” in Docker containers? Is this architecture often practiced?
Hello, I have a little theoretical question.
Is this normal, is it a common practice if all the necessary things for the site to work work in containers?
For example.
Container1: jenkins
Container2: MongoDb
Container3: java app
Container4: Grafana
.... and so on
Of course, the corresponding data and logs are taken out of the container and stored on the hard disk.
What is the probability that the Docker service will "go down" (may go down)?
Or in production - for everything, in the ideal case, should there be a car?
Thanks for the opinions.
Answer the question
In order to leave comments, you need to log in
It depends on the production and the "site". If this is a dynamically scalable web service on a cloud platform, then containers are just right. And if it's just a site on a VPS, then containers are not needed.
If you do use containers, then pack each individual element of the system in a separate container. And then the whole point of containerization is lost, it's easier to make a snapshot.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question