Event correlator does not generate any code.
The meta model is stored in a versioned document and the runtime engine executes (interprets) the meta model when events are delivered to trigger a workflow instance or resume an existing instance - while being fully aware of the state of each possible path.
The intent of the low code designer is preserved through the deployment and execution cycle and it never generates any code. The meta model of low code design is interpreted at execution time with full state dehydration into a persistent store.
New applications are yet another story in AWS costs in development, QA, load, staging and production environments.
The retail banker and customer interact multiple times to gather stipulations (documents), validate the application and kick off the loan process by payment of appraisal fees. However, the most critical resource, the underwriter is assigned only after all of these interactions have finished. This ability to interpret that execution has to wait as there is a possible live path upstream is a fairly complex problem in graph theory.
As displayed even though the three green activities have completed and the red activity is waiting to execute because all documents are not collected yet. The algorithm has deciphers that while there are two live tokens from “Validate application” and “Payment for Appraisal”, the third live token from “Submit documents” is yet to arrive as there is a live token in “Check all documents” step upstream. This token flow is the key to execution of control flow. As users lay error management on top of this, milestones at each stage and define global error handling based on what milestone the application is at; this secret sauce becomes the defining factor between success and failure to execute as per user intent. This is the holy grail where most workflow engines have traditionally failed.
Its all about the token!
The engine has horizontal n+1 scaling architecture as its completely stateless.
Multiple zones - fully HA
This is the low code designer which allows analysts to create the flows using a simple drag and drop tooling experience. If the user knows Flow charts or PowerPoint or VIsio, they would find it intuitive to create low code flows.
The heart of the low code platform. This is where the magic of long running processes and waiting for events occurs. This component leverages the strength of event driven architecture and combines that with cutting edge graph flow algorithms.
My founding team comprises two of the original authors of BPMN 2.0 specification at OMG(900+ citations and counting). Among us we are primary authors of seven joint patents in this space. Founding team
members have been working together for seventeen years
Vishal Saxena is the Founder and CEO of EventCorrelator. Recently, he was the founder of Roubroo, the call flow pioneer company, which was acquired by Avaya and is now incarnated as Avaya Engagement Designer.
Vishal is a well known researcher in the area of business processes and integration. He worked extensively on the BPMN 2.0 submission at OMG. His research has resulted in over ten patents and multiple papers with citations both in industry as well as academia.
Telephone: +1 650 245 3828
E-mail: info@eventcorrelator.com
Address: 3363 Louis Rd, Palo Alto CA 94303