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

.Net Workflow Software Engines

Posted by Dileepa WIjayanayake on Mar 8, 2019 8:55:00 AM

Just like physical engines, software engines today perform most of the heavy lifting  within a software application.  Software engines are typically running on a server, consuming many resources, spawning many threads, processes and executing code to perform functionality for the end user. We discuss the type of engines below in greater detail, and what you need to know. 

Whether its server based software, web based software or even standalone software, software engines play a key role in processing.  FlowWright uses 5 Microsoft .net based engines within the product to perform many of the functionality within the product. They are:

  • Workflow engine - executes workflow instances
  • ESB engine - processes published events to the Enterprise service bus
  • Archival engine - archives workflow instances, form instances and events
  • Triggers - processes email and file based triggers
  • Statistics - compute statistics and analytics for business processes

Architecture of these engines differ based on the functionality they provide to each of the modules within FlowWright; some do the work themselves, some spawn child processes to do the work.  These engines are also built to perform distributed computing, where many machines can distribute the load and process the load simultaneously.  

NETAPIWhere does Microsoft .Net play comes to play within these engines? Since FlowWright is built on the Microsoft technology stack/Microsoft technologies, these engines are architected to fully utilize the advanced features of .net.  Most times the FlowWright engines push the limits of .net when it comes to some of the very large workflows that are built and executed by our customers.

FlowWright prides itself that our engines are built from the ground up to produce the best performance. Within some of the other Microsoft based workflow technologies, such as .net, workflow cannot perform, making that a huge disadvantage to when it comes time to assess overall organization success.  So far, FlowWright engines have outperformed most workflow engines available on the market, this is proven by data provided by our customers. 

Microsoft .net based software engines can perform well, if they are designed well.

Talk to us today on how you can use FlowWright within your organization for automating processes.

New Call-to-action

Topics: .net workflow software forms, net workflow engine