<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Deployment architecture for Qlik Sense? (E.g. Equivalent to Extract, Transform, Load like 3 tier in QlikView?) in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Deployment-architecture-for-Qlik-Sense-E-g-Equivalent-to-Extract/m-p/1457421#M11683</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The essential point of using a multi-tier architecture is the division of work and this in general independent of the used tools. Therefore why not just re-using the already developed logic for Sense maybe with a few adjustments / improvements where things might be better splitted further or the opposite to simplified some things again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Jan 2018 14:10:32 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2018-01-02T14:10:32Z</dc:date>
    <item>
      <title>Deployment architecture for Qlik Sense? (E.g. Equivalent to Extract, Transform, Load like 3 tier in QlikView?)</title>
      <link>https://community.qlik.com/t5/Management-Governance/Deployment-architecture-for-Qlik-Sense-E-g-Equivalent-to-Extract/m-p/1457420#M11682</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the reccomended / suggested deployment architecture for Qlik Sense?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;E.g. In QlikView we had 3 tier architecture where there were Extract, Transform, and Load type folder structure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the suggestion / best practise around deploying something like this in Qlik Sense? Or What is the equivalant please?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2018 14:00:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Deployment-architecture-for-Qlik-Sense-E-g-Equivalent-to-Extract/m-p/1457420#M11682</guid>
      <dc:creator>mwallman</dc:creator>
      <dc:date>2018-01-02T14:00:29Z</dc:date>
    </item>
    <item>
      <title>Re: Deployment architecture for Qlik Sense? (E.g. Equivalent to Extract, Transform, Load like 3 tier in QlikView?)</title>
      <link>https://community.qlik.com/t5/Management-Governance/Deployment-architecture-for-Qlik-Sense-E-g-Equivalent-to-Extract/m-p/1457421#M11683</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The essential point of using a multi-tier architecture is the division of work and this in general independent of the used tools. Therefore why not just re-using the already developed logic for Sense maybe with a few adjustments / improvements where things might be better splitted further or the opposite to simplified some things again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2018 14:10:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Deployment-architecture-for-Qlik-Sense-E-g-Equivalent-to-Extract/m-p/1457421#M11683</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2018-01-02T14:10:32Z</dc:date>
    </item>
  </channel>
</rss>

