11 Replies Latest reply: Jun 8, 2018 9:36 AM by Levi Turner RSS

    8 node limit for Qlik Sense architecture

    Biju Krishnan

      After reading several documents, I have now formulated what I believe is the best possible Qlik Sense architecture (illustration below).

       

      By this I mean best practices recommended by Qlik via various documents have been incorporated. For example the deployment guide for AWS mentions the benefits of having a external load balancer (nginx or haproxy) and it makes a lot of sense. The STT published in October mentions the possibility of having a active secondary node.

       

      It would be nice to get some feedback on this illustration. I'm however wondering if the "8 node maximum" limit is going to stay long because with that my architecture would not scale horizontally. ie. I can only have two proxy nodes and two engine nodes and not more.

       

      QlikSense Architecture.png

      If I make the secondary node also a scheduler, I could add another engine node but that's about it.

       

      Is the 8 node limit therefore hard coded or is it just a soft limit defined by qlik support. In the beginning the above configuration will be more than sufficient for my client, but before I propose this I would like to know if scaling beyond 8 nodes would be a reality in the future.

       

      I have also seen some hints suggesting an architecture based on containers would be available in the near future which suggests that we would be able to scale beyond 8 nodes. Would be nice to hear some thoughts from the experts on this board.

       

      References

      1. STT - Failover in Qlik Sense.

      2. Qlik Sense on AWS - Deployment Guide

      3. Plan Qlik Sense deployments for version 3