You can configure a Qlik Sense enterprise deployment in a variety of different ways to suit the needs of your organization. For example, you can install Qlik Sense services to run on a single node or on multiple nodes for better performance and scalability. In a small single-node deployment, you deploy all services to a single server, which we do not recommend for larger organizations.
This section provides three examples of Qlik Sense deployments.
The following terms are used in the deployment scenarios:
- Central node: the central point for managing all nodes in a site.
- Scheduler or Reload node: reloads apps on a schedule, but does not serve content to users.
- Consumer node: serves apps to users, but is not used to create, process, or reload data.
- Development node: allows users to create and reload new apps, but does not serve normal consumer traffic.
- Proxy node: provides load balancing of user traffic to other nodes but does not contain a Qlik Sense Engine Service (QES).