News for hackers. Stuff that matters.

A comment on A Brand New “Workflow as Code” Execution Engine.

Re:A Brand New “Workflow as Code” Execution Engine by Towaway69 on Tuesday February 07, 2023 @07:56AM (#34692110)
How does this compare to something like Node-Red[0] which is also flow based?

[0]=https://nodered.org

[ Parent | on HN ]
Re:A Brand New “Workflow as Code” Execution Engine by jasfi on Tuesday February 07, 2023 @09:28AM (#34693164)
It seems node-red has a single-threaded execution engine, see: https://discourse.nodered.org/t/node-red-performance-benchma...

However this iWF can execute flows in parallel: "Parallel execution of multiple threads of business".

[ Parent | on HN ]
Re:A Brand New “Workflow as Code” Execution Engine by qlong-seattle on Tuesday February 07, 2023 @10:45AM (#34694246)
There are lots of things that other workflow engines cannot do:

Reset workflow : important to recover from bad states for any reasons. You may have bugs caused this or because downstream outages. Reset can let you go back like timing machines.

Search attributes: let you search for anything like having unlimited database index.

See more details in this article: https://medium.com/@qlong/iwf-vs-other-general-purposed-work...

[ Parent | on HN ]