What is the best way to organize access to Docker containers via FQDNs (full domain names)?

Question

linux

With coming !
the question is more for reflection and understanding of the Docker architecture!
there are several applications on the backend (5-10) that work in containers. All containers for now! fit on one host. We use a separate container for HAProxy. We launch them all (including the HAProxy container) using Docker Compose. At the moment, FQDNs are used to access containers, as required by individual applications. Containers only work on the internal ports of the Docker network and only the HAProxy container works on the external port (443). HAProxy routes requests for the appropriate FQDNs (for example app1.myhostserver.ru or app2.myhostserver.ru) to applications listening on specific ports on the docker network. I didn't install it myself... I don't know who did it, but it's interesting to ask the following:
1) Is this architecture the norm?
2) Is it possible to do without the HAProxy container and is it worth it?
3) How can this be improved?
Happy Holidays,
Vadim

Answer 1

In my opinion, there are two potential problems with this architecture - scalability and high-availability. That is, it does not support running containers on multiple servers and running multiple containers with a service.
If this is not required, then IMHO the configuration is quite normal. If required, then Kubernetes or another orchestrator is needed.