QlikView architecture

Now, let's look at the QlikView architecture using the following diagram:

In the QlikView architecture, the very first layer is the Data Layer. You bring the data from the external resources; for example, from an Excel file, from a database, or from the web. Once you get the data into the data layer from various sources, your data gets loaded with the help of the reload option into the QlikView Engine. The QlikView Engine is responsible for creating all the joints and queries by default, using its patented in-memory logic. What that means, is that QlikView creates the logic within the table, so you don't really have to write any SQL query, but, with the help of selections, you're generating the SQL query on the fly within the QlikView system with the help of the QlikView Engine. After that, you have the Presentation/Analysis layer, where you basically create the different types of charts and visualization, as well as filters for the consumption of the end user. After this, you have a Security layer, where you secure the data to make sure that the right information is available to the right user. QlikView has a very flexible security model. After that, the final layer is Application Publication. With the help of the QlikView server, you can publish your application on a QlikView server and distribute it to your end user, and they can view the application within their browser, or mobile, or in a tab, wherever they like. So, there you have it, that's your high-level introduction about QlikView architecture.