I'd also like to +1 on Cadence/Temporal. It's a really great mental model and framework for thinking about workflows. This is more of a proof of concept but it

I'd also like to +1 on Cadence/Temporal. It's a really great mental model and framework for thinking about workflows. This is more of a proof of concept but it can also support DSLs (although we found the go client is easier to understand than DSLs): https://github.com/checkr/states-language-cadence https://github.com/checkr/states-language-cadence