Overview
This type of deployment is typically used for production: tools such as failover and horizontal scaling can be used with this environment.
Adding Traefik to the environment provides a reverse proxy, load balancing and sticky sessions.
Remember, Yellowfin cluster deployments require a load balancer or a reverse proxy so that sticky sessions are available, but single Yellowfin instance deployments don't require load balancing nor a reverse proxy, as they are already stand-alone.
Choose your preferred deployment from the table below, then follow the instructions.
Deployment | Image | Description |
|---|---|---|
Yellowfin sandbox | All-In-One | A self-contained instance of Yellowfin. This is the simplest type of deployment. All content will be lost when the container is destroyed. |
Yellowfin single instance | App-Only | A single instance with a separate database, so data stored in the database will not be lost when the container is destroyed. |
Yellowfin multiple discrete instances | App-Only | Multiple instances each with their own dedicated database. This could be used to stage a development environment and a production environment during a proof of concept. |
Yellowfin cluster | App-Only | Multiple instances sharing a single database to form a Yellowfin cluster. This could be used to stage a clustered environment during a proof of concept. |