Distributed File Synchronization in FlowWright

Learn about the Distributed File Sync feature

Last published at: April 19th, 2024

In distributed processing environments where multiple FlowWright servers automate and integrate processes and systems, files must be synchronized across multiple servers.  FlowWright's Distributed File Synchronization feature accomplishes this.   In a typical customer scenario, where multiple servers are being used the challenge is to ensure all processes have access to real-time file and data info, regardless of which server created or houses the information.


For example, if a form is designed on “FlowWright app server1”, there are associated items created within the application file system, such as “CSS” and “js” files, that are required to render a form properly within a browser.  FlowWright's Distributed File Synchronization feature ensures any files created on server 1 will be automatically replicated on servers 2 and 3.  Server 1 creates a synchronization request, servers 2 & 3 will look for new synchronization requests and once requests are available, it will pull the files down to the server.

Furthermore, one application server can be separated into 2 roles, 1 for serving the user interface and 1 for processing the workflows.  The below diagram illustrates servers with 2 roles.


In the above scenario, the FlowWright UI server handles user interface web requests, and the workflow server only processes workflows.  In certain environments where there is heavy user traffic and heavy workflow processing, there are application bottlenecks due to infrastructure and resource limitations.  By separating the processing into 2 separate servers, optimal application performance and workflow processing performance can be achieved. 

Distributed File Synchronization is designed such that when adding more servers to the server cluster, those new servers automatically synchronize.