[ctvo]

> 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.

[qlong-seattle]

Maybe you can start with looking at the sample for solving the same "subscription" use case:

Temporal:

https://github.com/temporalio/subscription-workflow-project-...

https://github.com/temporalio/subscription-workflow-project-...

iWF:

https://github.com/indeedeng/iwf-java-samples#product-use-ca...

https://github.com/indeedeng/iwf-golang-samples#product-use-...

Note that you need to consider making changes to workflow -- in Cadence/Temporal, you must use versioning like: https://stackoverflow.com/questions/61298415/how-can-i-versi...

And this versioning/determinism constraints is just a small part of the learning curves for complicated project

And I am not the only one pointing this out. Also see the article from the principal of Azure Durable Function team:

https://medium.com/@cgillum/common-pitfalls-with-durable-exe...

[ctvo]

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.

[qlong-seattle]

Yeah this wiki page has exactly what you want to see here:

https://github.com/indeedeng/iwf/wiki/How-to-migrate-from-Ca...