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

Extending FlowWright - make it work the way you want

FlowWright is designed to be extended and expanded and many of our users push the product into new areas (which we love to see!)  To highlight all the ways FlowWright can be extended we summarize them below. 

Executing workflows in real-time using the FlowWright engine

The FlowWright low level API and engine API was built so that workflows can be executed in real-time with high performance.  Although this API has existed in previous versions, FlowWright v9.6 introduced Microservices, making it possible to call a workflow definition via FlowWright's REST API.  Under the hood of the Microservice, the low level API is used to execute workflows in real-time, or in memory. 

How to use NuGet FlowWright package

If you never heard of this product before you ma want to familiarize yourself with, NuGet.org as it is becoming very popular. Many developers use this website to include API packages to their software projects.  Why should teams use NuGet?  Typically when you want to use an API, you have to know what libraries/DLLs to reference; with NuGet all you have to do is to find the package and click install, then the NuGet package manager automatically downloads the selected package and its dependencies and simply adds them to your project.

Performance monitoring FlowWright engines

Performance monitoring is built into FlowWright workflow.  FlowWright uses performance instrumentation built into the Windows Operating system and leverages the performance monitoring and counters that are also provided by Microsoft Windows.

Things to consider when implementing Microservices

More organizations are adopting Microservices to run their business.  Like any kind of implementation, Microservices should be implemented properly in order to be effective and reliable.

FlowWright object model

Developers build most applications using a common design pattern.  That pattern can be object-based, object oriented, component-based, modular, etc...: some pattern exists.   FlowWright helps developers through use of a layered approach where modules are separated into components, and components break down into objects using a full object oriented design.

FlowWright high level API model

The FlowWright high level API is the main API for all FlowWright components, user interface, business logic, engines and gives all access to functionality and objects within FlowWright.  The API is divided into parent/child objects as described below:

Morphing processes at run-time

Morphing processes at run-time is a complex feature within our workflow product that allows users to create Dynamic Sub-workflows.  FlowWright is currently one of the only products on the market that is able to do this.  The real world example below might sound familiar.

Using Microservices as webhooks

Webhooks are very common today.  What are webhooks?  They are a way to get notified when something happens.  For example, if you like to get notified when a virtual machine shuts down in Microsoft Azure, just configure a webhook URL in Azure.  When the virtual machine shuts down at any point in time, it calls the configured webhook URL.  This method is much better than polling to see if the virtual machine has shut down.

Why managing Microservices can be difficult

"Microservices" was once just another buzzword, but now organizations have begun to understand their value and how they can significantly and positively impact business processes. The idea of Microservices arose from the difficulty of managing large systems so as to avoid duplicate functionality in different areas and from the efficiency that their re-useable nature would theoretically deliver.