Imagine having a suite of proven tools and technologies built for developers by developers that allows you to build highly-scalable, cloud ready solutions using the power of the Qlik Associative Engine. Well, imagine no longer last Friday, 4/6, we released the Beta of Qlik Core. Qlik Core is a development platform built on top of the Qlik Associative Engine. With Qlik Core, you can take advantage of the powerful associative indexing engine from Qlik to build your custom data exploration and data visualization solutions.
Please note that Qlik Core is a product - but it is not something you simply download and install with an installer. It works with technologies such as Node.js, Docker and Kubernetes and development knowledge of working with APIs is a prerequisite. To learn more about the Qlik Core Beta and to get started watch this brief video below and visit https://branch-blog.qlik.com/introducing-qlik-core-beta-30221d627132 - where our product manager John Trigg provides some more of the particulars. You can also visit the many getting started resources here https://qlikcore.com/.
This brief video below is a short promotional video designed to briefly introduce Qlik Core.
Hi Michael, what's the difference between QAP and QlikCore? At first sight I see that is something like a democratization of Qlik Sense apps just like QAP. What's your point of view?
Hi Marcel - the main difference is that it is designed to run within container software (Docker) which can run on Windows and Linux platforms, designed for custom deployments installed anywhere (in custom applications on premise in a cloud) and at cloud-scale. QAP is just the QIX engine decoupled from the UI and management components (so to speak) and only runs on Windows.
Thanks for the clarification! Another question - if we need to test a solution for more than 30 days in Qlik Core community version, is there a way we could go about doing that?
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)