12 ms·

> An activity must encapsulate something much higher level than a single IO operation. So something like "Configure BGP on a router", "Start a VM" etc. It needs

> An activity must encapsulate something much higher level than a single IO operation. So something like "Configure BGP on a router", "Start a VM" etc. It needs to be able to handle retries and thus be idempotent. I was referring to the workflows, that is, writing the workflows in managed languages, not the activities. Out of curiosity, are you working full-time on this? I'm working part-time on the same problem, looking to go full time soon, and it's interesting to see how the same ideas are popping up somewhat independently across different projects :) let me know if you're interested in chatting!

tomasol 1y ago
> I was referring to the workflows, that is, writing the workflows in managed languages, not the activities. Ah understood. I have no plans supporting native workflow executors. > Out of curiosity, are you working full-time on this? Yes, currently I work on it full time. > I'm working part-time on the same problem, looking to go full time soon, and it's interesting to see how the same ideas are popping up somewhat independently across different projects :) Nice website! I also see the ideas of determinism, replayability etc more and more. > let me know if you're interested in chatting! Sure, my email is visible in the Git commit history.