This section provides examples of how multi-node sites can be deployed.
The following terms are used in the scenarios:
- Central node: The node that is responsible for management activities and synchronization.
- Reload/scheduler node: A node that reloads apps on a schedule, but serves no content to users.
- Consume node: A node that serves apps to users, but is not used to create, process, or reload data.
- Development node: A node that allows users to create and reload new apps, but does not serve normal consumer traffic.
- Proxy node: A node that provides load balancing of user traffic to other nodes. This node does not contain a Qlik Sense Engine Service (QES).
Tip noteAn alternative to use a proxy node is to have a proxy installed on each consume node and balance the traffic using a hardware load balancer.