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

Workflow Process Engines

FlowWright utilizes several software engines to perform functionality within different parts of the application.  These software engines were architected and built from the ground up using the latest Microsoft .Net technology.  Our engines are built with performance in mind and designed for processing very large loads using distributed processing.

flowwright v9

  • Workflow Engine - all workflow instances are processed by the workflow engine.  FlowWright .net API or the REST API puts requests into the workflow engine for processing.
  • ESB Engine - the ESB engine processes all published events to the Enterprise Service Bus.  A separate high perform engine is designed to handle all event processing within FlowWright.
  • Workflow Trigger Engine - the trigger engine handles processing of all email and file based triggers.  The trigger engine monitors for events to happen and processes them.
  • Archival Engine - workflow instances, form instances and events can be archived within FlowWright.  Archival engine can be configured with many settings to perform archival within FlowWright.
  • Statistics Engine - the statistics engine collects and aggregates various configuration information and runtime information for analytics.

All engines within FlowWright are designed to execute in the following types of environments:

Based on the load being processed, all the above engines can be configured to execute on multiple machines using distributed computing.  In virtual environments, it's easier to increase the computing resources such as RAM, storage and virtual CPUs, but in an on premise infrastructure, hardware limitations exist.  In this case, multiple workflow servers can be configured to process distributed computing-which is high value to the users. 

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