Qlik Community

Qlik Sense App Development

Discussion board where members can learn more about Qlik Sense App Development and Usage.

Announcements
BARC’s The BI Survey 19 makes it official. BI users love Qlik. GET REPORT

Should QlikView's 3-layer architecture be used in Qlik Sense?

In QlikView applications, the so-called 3-layer architecture is often used:

  • Layer 1- Extract: Extract data from sources and save it into QVD files "as is".
  • Layer 2 - Transform: Load QVD files and make all necessary transformations according to business needs.
  • Layer 3 - Presentation: Binary load the previous layer and create the dashboard for the end user.

Is this architecture recommended for Qlik Sense too?

Tags (2)
1 Solution

Accepted Solutions
Highlighted
MVP
MVP

Re: Should QlikView's 3-layer architecture be used in Qlik Sense?

The Qlikview 3-layer architecture is just as appropriate with Qlik Sense.


Qlik Sense is hardly different from QlikView when it comes to load scripts. The 3-layer architecture is based entirely of a layering of the load process. The separate organisation into 3-layer makes absolutely sense still for the same reasons as it does for QlikView.

View solution in original post

2 Replies
Highlighted
MVP
MVP

Re: Should QlikView's 3-layer architecture be used in Qlik Sense?

The Qlikview 3-layer architecture is just as appropriate with Qlik Sense.


Qlik Sense is hardly different from QlikView when it comes to load scripts. The 3-layer architecture is based entirely of a layering of the load process. The separate organisation into 3-layer makes absolutely sense still for the same reasons as it does for QlikView.

View solution in original post

joblette
New Contributor II

Re: Should QlikView's 3-layer architecture be used in Qlik Sense?

However, if you plan to use Qlik Sense Cloud Business, I think it is good to know that this architecture currently doesn't work because:

- Store are not possible

- Binary load are not possible