I have an idea regarding engine design i want to share with you. But first, it
seems like we need a small overview of the current implementations.
I'm not sure how ML will react on a bunch of ASCII graphs, so here is an
etherpad:
I am in the full agreement with the proposed approach (risked to copy below,
let's see if email handles your diagrams):
* Single Engine handles multiple executions asynchronously, in non-blocking way.
* Persistence access only from API and/or Engine, Engine writes, API reads.
* Action runes
