<?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 How does Activiti achieve scalability in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/how-does-activiti-achieve-scalability/m-p/191953#M145083</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Can anyone describe how Activiti scales? I'm particularly interested in where application state resides and how the database can be scaled (horizontally/vertically). Are there any single points of synchronisation?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 16 Oct 2014 15:19:28 GMT</pubDate>
    <dc:creator>moldy</dc:creator>
    <dc:date>2014-10-16T15:19:28Z</dc:date>
    <item>
      <title>How does Activiti achieve scalability</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/how-does-activiti-achieve-scalability/m-p/191953#M145083</link>
      <description>Can anyone describe how Activiti scales? I'm particularly interested in where application state resides and how the database can be scaled (horizontally/vertically). Are there any single points of synchronisation?</description>
      <pubDate>Thu, 16 Oct 2014 15:19:28 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/how-does-activiti-achieve-scalability/m-p/191953#M145083</guid>
      <dc:creator>moldy</dc:creator>
      <dc:date>2014-10-16T15:19:28Z</dc:date>
    </item>
    <item>
      <title>Re: How does Activiti achieve scalability</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/how-does-activiti-achieve-scalability/m-p/191954#M145084</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Activiti is designed to be stateless for any commands against a process instance or task. So you can use multiple engine instances on one database without any problem. When you use multiple engine instances you should only decide if you want the job executor component to run on every engine instance as well. In the current default job executor every job executor will try to lock a job and execute it. We'll have a new lock free job executor coming up in the next release however.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Oct 2014 06:41:01 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/how-does-activiti-achieve-scalability/m-p/191954#M145084</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2014-10-17T06:41:01Z</dc:date>
    </item>
  </channel>
</rss>

