Workflow engines vs hand-built sagas
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
decide between a workflow engine (such as Temporal or Camunda) and a hand-written saga.
Planned topics
- Engines give durable state, timers, retries, and visibility for long, branching processes.
- They add a new platform to run, a programming model to learn, and a dependency.
- One short saga with two steps rarely justifies an engine; many long ones often do.
- Criteria: number of workflows, duration, human steps, need for audit and visibility. Verify product details before recording.
Draft outline details
Demonstration
a comparison table with rows durability, retries/timers, visibility, learning curve, operations, lock-in; two columns: hand-built (outbox + state table) vs engine.
Check your understanding
Name a sign that an engine is justified.
Show answer
Many long-running, multi-step processes with timers or human tasks needing visibility.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.