conductor-workflow-authoring

You define a Saga workflow in Netflix Conductor by authoring JSON definitions that map domain steps to task types and capture compensation paths. This moves complex orchestration logic into versioned artifacts.

Conductor orchestrates long-running business processes by pairing JSON DAG definitions with external Go task workers. This separates orchestration logic from worker code to manage branching and fault-tolerant execution.

To implement idempotent workers for Conductor task types, you write external Go task worker logic that safely handles retries. This ensures long-running business processes can recover from failures without duplicating side effects.

The best way to handle workflow retries and timeouts in Conductor is to apply orchestration policies directly within your JSON definitions. This makes resilience patterns and failure workflows explicit and reviewable.

Yes, you can use Conductor for parallel process orchestration by mapping domain steps to task types like FORK_JOIN. Your JSON definitions will clearly define both the happy path and the failure compensation logic.