#workflowdefinitionlanguage — Public Fediverse posts

Running into issues with #AirFlow and sub-DAGs, and now I'm reading about #CommonWorkflowLanguage and #WorkflowDefinitionLanguage and wondering how they map onto #FlowBasedProgramming.

I'm having the same issue as Twine was having over at web.archive.org/web/2019091209… which I suppose I could solve the same kind of brute-force way they did, but it's easy to start diverging into more research.

I'm looking at Toil(0) and Arvados(0) and what they can do.

(0) toil.readthedocs.io/
(1) arvados.org/

I strongly suspect we'll end up just not running a workflow engine down the road. Our use case is not super complicated, but the workflow engine integration is turning out to be. The whole flow status monitoring UI *is* nice to have though.