Loosely Coupled and Intelligently Integrated Workflow

Learn about the merits of FlowWright workflow engine and ESB engine

Last published at: April 18th, 2024

As the technology industry is involved, so do the process flow products. FlowWright adapts to industry change by utilizing component-level architecture that loosely couples and intelligently integrates across systems. You might ask what’s all this about, so here it is:

FlowWright’s built-in designer with many out-of-the-box steps provides you with many intelligent steps that perform various tasks/functionality without coding. If we don’t provide a step/piece of functionality, simply get your developer to build a custom step to perform that functionality. FlowWright’s loosely coupled architecture provides this flexibility many other platforms don't.

Many comparative workflow products are rigid and offer users only the option to work within their framework or architecture; FlowWright has an open-door policy. You can build the way you want within FlowWright. FlowWright also adapts easily to graphical decision-making from a design and run-time perspective. The workflow designer is driven by FlowWright’s powerful configuration, where flexibility is the focal point of our product.

Now comes the intelligent part, today’s processes perform actions across systems, sometimes across many-many systems. Integration between systems not only has to be seamless, but also intelligent. Intelligent integration is not possible with most systems, given the use of API-application integration points of an external application, whether the API is REST or DOT NET. The process engine must be intelligently integrated with systems and FlowWright accomplishes this in 2 ways: one by the use of custom steps that were built with intelligence and the second being the Enterprise Service Bus (ESB) with event-based integration.

So, what about the engines, how intelligent are they? FlowWright’s workflow engine and the ESB engine both have smarts built into them, they can adjust themselves. For example, our engines go into a slower pace when there’s no work to be done, and here are the benefits of that:


  • Reduces network chatter – less network traffic gives better network performance and also reduces costs within cloud environments
  • Less database calls – no work means, fewer calls coming into the database, smaller transaction logs, and less memory consumption by the database

Engines are also smart in how child processes are launched, this is very important to determine how the workflow processes are using server resources to process them. Given some environments, resource-heavy applications can bring down a server. FlowWright manages this well, through the configuration, by which the number (#) of child processes to launch can be managed, and also how often to launch can be managed.

Intelligent integration always comes at a price, and the price is CPU usage, analyzing existing run-time data to perform better always costs more from the CPU side. This is not an issue in today’s most cloud environments, where allocated CPUs to a VM are fully available to that VM.