A Workflow-As-Code microservice orchestration platform for building resilient, fault-tolerant, and scalable long-running processes.
iWF (Indeed Workflow Framework) is a Workflow-As-Code microservice orchestration platform that provides a coding framework and service for building resilient, fault-tolerant, and scalable long-running processes. It streamlines workflows that involve waiting on external events, handling timeouts, and persisting state over long durations, enabling developers to create maintainable workflows that adapt to real-time events and integrate with external systems.
Developers and engineers building complex, long-running microservice orchestrations, such as SAGA patterns, user sign-up flows, subscription management, and AI agent workflows, who need resilience and scalability.
iWF offers a simplified, structured programming model with Workflow-As-Code, durable timers, automatic retries, and extensive tooling, making it easier to build and maintain resilient workflows compared to lower-level orchestration frameworks.
iWF is a Workflow-As-Code microservice orchestration platform offering an orchestration coding framework and service for building resilient, fault-tolerant, scalable long-running processes
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Defines workflows in native code with explicit branching, looping, and parallel threads, making complex logic like SAGA patterns maintainable and natural to read, as shown in the samples.
Automatic retry with durable timers ensures workflow resilience to failures, reducing the need for custom error handling code and background execution units.
iWF applications are REST-based microservices, facilitating easy deployment, monitoring, and scaling with industry-standard tools and practices.
Provides extensive tooling for runtime state lookup, timer skipping, and workflow resetting, enhancing debuggability and management without manual intervention.
Requires running both the iWF server and a backend engine like Temporal or Cadence, increasing infrastructure and operational overhead compared to all-in-one solutions.
Only supports Java, Golang, and Python SDKs, excluding other popular languages like JavaScript or C#, which can limit adoption in diverse tech stacks.
Key concepts and tutorials are scattered across GitHub wiki, Medium articles, and sample repos, making onboarding and troubleshooting more challenging for new users.
The layer on top of Temporal/Cadence introduces performance latency and ties users to iWF's evolution, potentially creating vendor lock-in and dependency issues.