iwf

Main repo(with docs/wiki/discussion): https://github.com/indeedeng/iwf Samples: https://github.com/indeedeng/iwf-python-samples

Yeah this wiki page has exactly what you want to see here: https://github.com/indeedeng/iwf/wiki/How-to-migrate-from-Ca...

You don't have to run elastic. Cadence/Temporal let you run only with database for majority of the feature/power. ElasticSearch is only for supporting the searching functionality(advanced visibility). https://docs.temporal.io/visibility https://cadenceworkflow.io/docs/concepts/search-workflows/ Same as in iWF, you can use a Temporal service without advanced visibility. E.g. this doc is showing how to run with Temporalite which doesn't have advanced visibility with it. https://github.com/indeedeng/iwf/blob/main/CONTRIBUTING.md#o... Again, you still have 90% power and the only thing missing is searching for workflows using "search attributes". You can still store data in search attributes but they are just not searchable. And later, you can migrate to a Cadence/Temporal service that has advanced visibility enabled.

Congratulations on your release! I have 2 interrelated comments: the "If you are not [familiar with Cadence]" link <https://github.com/indeedeng/iwf#if-you-are-not> seems to go to a WIP Google Doc, so I would suggest a more tl;dr version instead of linking out to Google Docs. Related to that, it would be great if the "supporting docs" were either in the repo's wiki or in the repo, because it has been my experience that Google Docs (and its Slides friend) are 404s waiting to happen when the owner forgets they're shared or Google "does a Google" and bans accounts Maybe I'm not the target audience for this because I don't already know what pains Cadence causes, as that seems to be about 80% of the message here, but I do love workflow engines and thus want to understand how this solves Cadence problems but doing independent research into Cade

It's built on top of Cadence Temporal(Similar to AWS SWF, Microsoft Azure Durable Function) by expert of Cadence/Temporal to provide clean and simple API/interface for development. * Easy to understand and get started * Easy to make changes -- no non deterministic errors and no need to write versioning code. * Easy to write and maintain unit tests * Easy to monitor and operate * Provide all power of Cadence/Temporal（scalability/reliability) Look at the samples for how easy it is, and try it out!