An order workflow checks inventory, charges payment, and requests shipping in sequence.
Track execution state and retries without embedding the workflow in application code.
Which AWS service is most appropriate?
AWS Step Functions defines state transitions, branches, retries, and execution history for multi-service workflows.
Detailed explanation
WAF inspects web requests and does not orchestrate business steps.
WAF inspects web requests and does not orchestrate business steps.
Step Functions manages state transitions, retries, branches, and execution history.
Step Functions manages state transitions, retries, branches, and execution history.
Route 53 health checks support DNS failover and do not order business processing.
Route 53 health checks support DNS failover and do not order business processing.
An S3 policy controls access and does not manage an application workflow.
An S3 policy controls access and does not manage an application workflow.
Check official documentation
Compare the following points with the official documentation.
AWS Step Functionsのステートマシンと実行履歴の公式説明を確認する。
What to confirm
複数サービスの処理を状態遷移として管理できる。
Key points
- AWS Step Functions
- State machine
- Retry
- Execution history
Notes
- Environment: AWS公式Step Functionsドキュメントの確認
- Confirm current AWS architecture guidance and service behavior in the official documentation.
Foundation review
Orchestration
The workflow definition coordinates separate services without hiding the sequence in one function.
Failure handling
Retries and branches make expected transient failures explicit and observable.