> Cadence workflow is powerful, but hard to learn and use. Though documentation and samples look straightforward to write a HelloWorld or a demo, many Cadence users run into issues to write complicated workflows and maintain/operate it in production.
This is the problem statement from their design document. I'm not sure I agree with it. This appears to be an abstraction over defining Temporal / Cadence workflows.
I think being straight forward about how iWF solves the issues you and others have brought up straight on the landing page will do you a lot of favors.
- Dimension A in Temporal, in iWF
- Dimension B in Temporal, in iWF
...
- Here's when you want to use Temporal directly. Here's when you should use iWF.
I'm still unsure how iWF solves the items brought up in the blog post you linked.
This is the problem statement from their design document. I'm not sure I agree with it. This appears to be an abstraction over defining Temporal / Cadence workflows.