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.
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.
Microservices workflow can be architected in many ways; most depend on a lot of custom code, or modules strung together that then provide workflow Microservices. FlowWright takes a different approach to designing Microservices with the users in mind. We share more below.
You see your doctor, and the doctor says you have high cholesterol and need medication. The doctor's office sends off your prescription for cholesterol medication to the pharmacy. You get a call from the Pharmacy and the medication is ready to be picked up. This process used to be a couple of days, but now with workflow technology you can pick it up in less than an hour.