Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.
Client is looking out for distributed archicture for Qliksense , can you please suggest how many layer of architecture is possible in Qliksense.
Do you have an architecture diagram or list of services which can be distributed on multiple servers. In Qv 11 we had a proper documentation on the same.
The Qlik Sense services are:
The Qlik Sense Repository Service (QRS) manages persistence and synchronization of Qlik Sense apps, licensing, security, and service configuration data. The QRS attaches to a repository database and is needed by all other Qlik Sense services to run and serve Qlik Sense apps. The QRS also manages the synchronization used within multi-node Qlik Sense sites. In addition, the QRS stores the Qlik Sense app structures and the paths to the binary files (that is, the app data stored in the local file system).
In a default Qlik Sense installation, a Qlik Sense Repository Database (QRD) service is created specifically for use by the Qlik Sense Repository Service (QRS). The QRS connects to the QRD to read and write data in the repository database. A PostgreSQL database is used by default. l
The Qlik Sense Proxy Service (QPS) manages the Qlik Sense site authentication, session handling, and load balancing.
The Qlik Sense Scheduler Service (QSS) manages the scheduled reloads of Qlik Sense apps as well as other types of reload triggering (for example, task chaining) based on other task events.
The Qlik Sense Engine Service (QES) is the application service, which handles all application calculations and logic.
A Qlik Sense multi-node site is usually deployed on an intranet in order to allow developers and users to:
Create and reload content l