Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Iwf Alternatives
Similar projects and alternatives to iwf
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
process-compose
Process Compose is a simple and flexible scheduler and orchestrator to manage non-containerized applications.
-
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
iwf reviews and mentions
- Show HN: Python SDK for iWF – API orchestration engine
- A new Workflow engine to orchestrate micro services for building reliable, fault-tolerant, and scalable applications, faster than ever
- Build reliable, long-running Golang applications faster than ever
-
A Brand New “Workflow as Code” Execution Engine
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 Cadence just to know what makes iWF better is too much to ask, IMHO
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.
-
A note from our sponsor - InfluxDB
www.influxdata.com | 17 Apr 2024
Stats
indeedeng/iwf is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of iwf is Go.