<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=287945&amp;fmt=gif">

Infrastructure Configurations

FlowWright supports many infrastructure configurations.  FlowWright can be installed and configured to run on a single server or on many servers for distributed processing.  Here are the list of possible configuration, starting from the most basic:

FlowWright basic configuration

Although FlowWright can be installed and run on a single server, we recommend separating the application server from the database server, mainly for performance.  But, its possible to run all on one server.  FlowWright can be installed on Cloud environments, virtual environment or on hardware infrastructure.

Supported environments for FlowWright

FlowWright is designed for distributed processing, as your processing loads increase, you have 2 options, either increase the computing resources or add more distributed workflow servers.  In virtual environments its pretty easy to increase the computing resources, for example, if the virtual machine only has 2 CPUs and 8 GB of RAM,  it can be easily increased to be 4 CPUs and 16 GB of Ram.  But on on premise or co-located infrastructure  server, its not easy to upgrade hardware that easily, in cases like that FlowWright let's you add multiple workflow servers, also called distributed processing.  Below diagram is a visualization of how that is accomplished.

 FlowWright distributed servers

Some of our large customers who process large # of workflow instances in an hours require a lot of computing power.  They typically configure their FlowWright infrastructure using the distributed configuration.  Distributed FlowWright servers have the smarts built-in not to step on each others work and also built to perform, performing true distributed computing for workflow processes.  With multiple application servers, its also a good idea to use a load balancer with the sticky bit on to distribute the user load.

FlowWright can be also installed on 2 application servers, where the user interface is served by one server and the other server running the FlowWright engines.  The last configuration that is possible with FlowWright is multi database processing by a server.  This is similar to how Saas environment handle multi tenants, each FlowWright database could represent a tenant in a multi tenant environment.  Configuration looks as follows:

FlowWright processing multiple databases

As shown in the above diagram, multiple databases can be processed by a single FlowWright server or a # of FlowWright servers.  FlowWright can be configuration using many different configurations, each of the FlowWright servers do require proper licensing, please contact sales for licensing questions.  For FlowWright infrastructure requirements, click HERE.

FlowWright is built to perform, performance is #1 when it comes to workflow processing.  Our customers execute mission critical applications with mission critical workflow processes.  FlowWright is able to perform with optimum performance. 

Here's an example of that, we have a large automotive client in Europe who had to perform plan shut down around the world, 250 plants to be exact.  These had to be shut down at different times, and ~80,000 tasks had to be routed to user around the globe within a 48 hour period.  FlowWright routed a task every 1.5 seconds to someone around the globe, that's performance FlowWright is built for.

New Call-to-action
Still Need Help? Seach Through Our Resources Or Talk To A Team Member!