What is iWF#

iWF streamlines workflows that involve waiting on external events, handling timeouts, and persisting state over long durations. With iWF, developers can build scalable, maintainable workflows that adapt to real-time events and integrate seamlessly with external systems. iWF is heavily used by Indeed engineering teams to power millions of workflows every day.

What Makes iWF Unique#

• Workflow-As-Code uses native code to define everything: branching, looping, parallel threads, variables, schema etc.
• Simplified Architecture: iWF applications are all REST based micro-services which are easy to deploy, monitor, scale, maintain(version) and operate with industry standards.
• Simplicity and explicitness of APIs: uses as few concepts as possible to model complex logic. It uses clear abstractions to defines workflows in terms of discrete states, with waitUntil conditions and execute actions, declarative schema for data and search attributes for persistence, and RPC for external interaction for both read and write.
• Dynamic Interactions: allows external applications to interact with running workflows through RPC, signals, and internal channels.
• Extensive tooling: provides tooling to look up running state definitions, skipping timers, enhanced resetting etc.