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

Batch versus Real-Time .NET Workflow Processing

Posted by Dileepa WIjayanayake on Feb 24, 2020 10:05:58 AM

FlowWright's Enterprise Workflow Software uses several engines to process functions across its  platform.  All workflow processes are processed using the workflow engine service.  The engine service runs as a Windows service and processes workflows when work needs to be performed.  The work is then done by child workflow processes launched by the service and these child processes all use the core workflow engine.

By default, the engine runs in background mode: the service checks for work and when there’s work available then it performs the work using the engine. This background mode is good for processing large volumes of workflows as work becomes available.  In most cases, the engine is processing workflow from the beginning of the workflow, or from a step within the workflow, for example, a wait step or a task step.  One difference from other workflow products is that when our workflows are sleeping/or waiting, our engine consumes zero resources.  Workflows are persisted in the database and sleep until there is work to be done.

FlowWright also has a real-time execution mode, where the engine can execute a workflow completely in memory without any communication with the database.  There are many use cases where you might want to do this: high-speed processing or computations, decisions, and more.  Here are 3 main areas where this feature is utilized within FlowWright functionality:

Microservices are always executed in real-time because a Microservice represents a REST API call that must return a value.  Similar to Microservices, a real-time form computations UI control also executes workflow in real-time to display the results on a form.

In version 9.6.1, we have made the API more accessible by providing a real-time execution method.

real-time engine execution API call

The above method will execute a given workflow in memory and provide the execution result back to the caller.  We see more and more customers using the real-time execution features of FlowWright's workflow engine, especially where information needs to validated at high speed.

Come learn about FlowWright real-time engine execution today.

New Call-to-action

Topics: workflow automation