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.
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.
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.
"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.
FlowWright was built with two mandates: 1) "keep it intuitive" and 2) "do it your way". Most BPM/Workflow products require users to implement everything within their platform ecosystem. Users often learn the hard way that this restrictive approach makes it difficult to accomplish your goals successfully or efficiently. This blog explains why workflow without limitations is the best approach.
When new clients onboard the FlowWright workflow platform we ensure that they are set-up for success by ensuring all team members have completed our 4 day on-site Training Program.