Page History

...

1. Docker Master Node 
2. Docker Swarm Worker Node(s): Yellowfin containers sit within the worker node or nodes of a Docker Swarm environment.   
3. The Yellowfin component: Yellowfin containers that make up the Yellowfin cluster have been deployed over multiple Docker worker/slave nodes in a Docker Swarm cluster. Unlike Traefik, there is no restriction to which nodes the Yellowfin containers can be deployed to. Depending on the Yellowfin deployment type that was chosen, the Docker environment will have one or more Yellowfin instances running, with those instances connecting to either the same database (for a clustered Yellowfin deployment) or different database (discrete instance deployment). In this diagram, they connect to the same database. 
4. DBMS: For performance reasons, we currently recommend not running the repository database in a Docker container for production workloads. Instead, we recommend a dedicated database server; for example, for AWS, an EC2 instance or using AWS RDS. 
5. Traefik: Traefik is a container-aware reverse proxy that runs on the manager node(s) in a Docker Swarm environment — due to it needing access to the Docker Swarm API — and handles the load balancing and sticky sessions for the Yellowfin containers. If you don’t wish to use Traefik (for example, you already use Nginx), you can use your own preferred load-balancing tool, provided it supports sticky sessions. We go into more detail about Traefik and about Traefik and Docker swarm later on (link). 
   

...