Scalability

When talking about the scalability of flowable engage, the different nodes can be divided into three main groups. The first group are the proxy nodes, which are responsible for processing network traffic. The second group, the processing nodes, are responsible for the handling of documents and requests. And the third group, the User Interactivity Nodes are responsible for processing user requests.

Proxy Nodes

Proxy nodes are stateful. In relation to scalability it is important to understand that they are handling network traffic which means that the number of sessions and the percentage of used network bandwidth are key indicator for their workload. Additional to the number of sessions the CPU utilization is another important indicator.

(Pre-) Processing Nodes

For the (pre-) processing nodes the amount of data processed is the key indicator if additional resources are needed. This is mainly influenced by the amount (and size) of the files to process. Secondary indicators are CPU and RAM utilization.

User Interactivity Nodes

User interactivity nodes are handling the user interaction and therefor their workload is mainly depended on the amount of users and their behaviour. The number of concurrent user sessions and interactions is a key factor to evaluate the workload on the system. Secondary indicators are CPU and RAM utilization.

Basic High Availability Setup

Type Amount

Proxy Nodes

2

Processing Nodes

2

User Interactivity Nodes

2

Scale out recommendations

Flowable Engage Components

It is recommended to add an new node of the matching type if the other nodes of this group match one to the trigger criteria. Additionally to the trigger criteria it is recommended to scale out the components in an even matter. This means not to add much more nodes of one type without adding the same amount of others. The difference to an even distribution should not exceed 50%.

Type Basis Trigger

Proxy Nodes

2

network bandwidth used > 80%
CPU or RAM usage > 80%

Processing Nodes

2

CPU or RAM usage > 80%
theoretical max. I/O over time > 60%

User Interactivity Nodes

2

CPU or RAM usage > 80%

Third party components

Recommended sizing and configuration of third party components are described in other documents (e.g. DB Sizing Documentation) and not part of this document. The following indicators show proposed trigger criteria to scale out the components.

Type Trigger

NFS

Free storage capacity < 20%
CPU or RAM usage > 80%

Oracle DB

Free storage capacity < 20%
CPU or RAM usage > 80%

Elastic Search Cluster

resize cluster according to configuration when parts or whole cluster have a bigger workload than 80% of maximum capacity.

Disclaimer

Flowable AG may change, amend or delete information contained in its documents at any time and without formal arrangement. Documents and other informational items concerning a release of Flowable Engage that has not yet been officially released by Flowable AG are non-binding and may be incomplete or contain errors. Flowable AG strives to provide complete and exact information in its documents. If permitted by applicable law, Flowable AG takes no responsibility for the accuracy of the issued informational items and documentation and does not provide any warranty for their content. Flowable AG assumes no liability for any direct, indirect or incidental damages incurred by the use of its documents and informational items. Documents or informational items do not change or amend the contractual terms and conditions regarding Flowable Engage. For improved readability, the documentation uses male pronouns for all persons. It does, however, address both male and female readers to the same extent.