Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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.
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.
Accepted Solutions
Thanks Levi. Here is a screenshot from the Nov 2017 Plan and deploy guide. Clearly says 8 nodes is the supported limit.
ok good to know that you work for Qlik Support. And you right that there is a faint mention of the node limit being that for engine nodes, in the youtube video where you present shared persistence.
I would look at the plan and deploy guide which is available via the product download page. I'm adding the link here but if you are unable to access it please find it from the product download page and by selecting Qlik Sense and November 2017 as the options in the filter.
https://da3hntz84uekx.cloudfront.net/QlikSense/11.24/2/Plan%20and%20deploy%20Qlik%20Sense.pdf
Other than the difference of opinion on the node limit - do you have some feedback on this architecture diagram?
I have combined information from a variety of documentation and STT videos to come up with that diagram. The qlik documentation unfortunately does not seem to catch up with the developments. For example STT for failover clearly mentions that any node could be designated as a secondary node (active-active) but the Plan and Deploy guide does not seem to capture this change in stance.
ok good to know that you work for Qlik Support. And you right that there is a faint mention of the node limit being that for engine nodes, in the youtube video where you present shared persistence.
I mean I was the person who did those presentations 
Grazie. I'll log that as a doc bug.
For example STT for failover clearly mentions that any node could be designated as a secondary node (active-active) but the Plan and Deploy guide does not seem to capture this change in stance.
Can you specifically mention what is misaligned? I'd prefer the specificity about what you find issue with rather than what my eyes find off.
