Local System Integration v2

Use a local Cluster when a Workflow must reach systems or resources that are not available from Flowgear's cloud runtime.

Design

Split the steps in the solution according to whether they should be run at a local or Cloud cluster.

Use a local Cluster for steps that need to interact with resources that are not published to the Internet as well as adjacent steps that will run more efficiently from a local Cluster.

Use the cloud Cluster for high-bandwidth interaction with Internet-facing services.

You can trigger a local Cluster Workflow directly from HTTP by adding an HTTP receive step into it. When an appropriate call is received at the Cloud cluster, the Workflow will be activated on the local Cluster transparently.

Availability

Install more than one host in a local Cluster to provide high availability. Ensure each host has access to all of the resources (for example, endpoints and services) that are required by the Workflows that run on it.

Flowgear will manage load balancing across multi-host local Clusters and will automatically fail over to an available host when one becomes unavailable.

See also

See Create a Listener Workflow, Connection, and Workflow Designer Top Bar.