<?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: RTDM Runtime Load Balancing in SAS Customer Intelligence</title>
    <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Runtime-Load-Balancing/m-p/538315#M1124</link>
    <description>&lt;P&gt;Hi, yes - that's one of the possible and feasible options that we utilize with some of our clients. That's not the only option (there exist other architectures, including using a 3-node clustered runtime environment with clustered metadata server), and combination/hybrid approaches with even higher number of servers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But what you are suggesting is possible and will work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are always pros and cons in choosing deployment architecture (including RTDM runtime high-availability and load balancing architecture), and there is no single silver bullet - you can't tell whether one option or another is better without a deep dive into a particular client situation, requirements, technical and organizational dependencies, priorities, etc.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;One specific implication of the architecture you suggested is that every diagram change will need to be deployed twice, manually (on environment&amp;nbsp;1 and environment 2). It's an overhead, but also sometimes a benefit.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not sure about your question ("&lt;SPAN&gt;&lt;EM&gt;How to achieve Load balancing for the above 2 runtime servers&lt;/EM&gt;") - you have responded to that yourself, just one line ago ("&lt;STRONG&gt;Active-Active Setup with HTTP Load Balancer / F5&lt;/STRONG&gt;") - that's how (on a high level). Or are you asking about more details of how to leverage F5 for that purpose?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 25 Feb 2019 16:05:10 GMT</pubDate>
    <dc:creator>Dmitry_Alergant</dc:creator>
    <dc:date>2019-02-25T16:05:10Z</dc:date>
    <item>
      <title>RTDM Runtime Load Balancing</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Runtime-Load-Balancing/m-p/538196#M1123</link>
      <description>&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;May I know your thoughts for below RTDM architecture please:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Setup:&lt;/P&gt;&lt;P&gt;-Two RTDM Runtime Servers&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; a. RTDM Runtime 1 (Standalone - Meta/Compute/Midtier)&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; b. RTDM Runtime 2 (Standalone- Meta/Compute/Midtier)&lt;/P&gt;&lt;P&gt;- Active-Active Setup (with HTTP Load Balancer / F5)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How to achieve Load balancing for the above 2 runtime servers?&lt;/P&gt;&lt;P&gt;Any docs for reference as well?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Mon, 25 Feb 2019 06:33:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Runtime-Load-Balancing/m-p/538196#M1123</guid>
      <dc:creator>tlorel</dc:creator>
      <dc:date>2019-02-25T06:33:20Z</dc:date>
    </item>
    <item>
      <title>Re: RTDM Runtime Load Balancing</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Runtime-Load-Balancing/m-p/538315#M1124</link>
      <description>&lt;P&gt;Hi, yes - that's one of the possible and feasible options that we utilize with some of our clients. That's not the only option (there exist other architectures, including using a 3-node clustered runtime environment with clustered metadata server), and combination/hybrid approaches with even higher number of servers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But what you are suggesting is possible and will work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are always pros and cons in choosing deployment architecture (including RTDM runtime high-availability and load balancing architecture), and there is no single silver bullet - you can't tell whether one option or another is better without a deep dive into a particular client situation, requirements, technical and organizational dependencies, priorities, etc.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;One specific implication of the architecture you suggested is that every diagram change will need to be deployed twice, manually (on environment&amp;nbsp;1 and environment 2). It's an overhead, but also sometimes a benefit.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not sure about your question ("&lt;SPAN&gt;&lt;EM&gt;How to achieve Load balancing for the above 2 runtime servers&lt;/EM&gt;") - you have responded to that yourself, just one line ago ("&lt;STRONG&gt;Active-Active Setup with HTTP Load Balancer / F5&lt;/STRONG&gt;") - that's how (on a high level). Or are you asking about more details of how to leverage F5 for that purpose?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Feb 2019 16:05:10 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Runtime-Load-Balancing/m-p/538315#M1124</guid>
      <dc:creator>Dmitry_Alergant</dc:creator>
      <dc:date>2019-02-25T16:05:10Z</dc:date>
    </item>
  </channel>
</rss>

