Building advanced workflows with AWS Step Functions
summary
Shows how AWS Step Functions replace glue code with concrete patterns: use states.uuid intrinsic instead of a Lambda to save transitions, nest standard + express workflows to cut million‑run cost from $42 to ~$13, and choose standard for callbacks/long jobs and express for sub‑5‑minute high throughput. Demonstrations include converting many Lambdas into a single REST‑as‑workflow for an espresso cart, a saga pattern for multi‑step rollbacks, and launching ECS tasks from Step Functions for long video processing.
AI-written summary · about
chapters (12)
- 0:00Introduction to session
- 1:39What are Step Functions
- 5:16When to use Step Functions
- 8:00Real-world workflow examples
- 10:55Standard vs Express workflows
- 14:04Choosing workflow types
- 14:46Nesting workflows for cost
- 16:55Reducing Step Functions costs
- 19:22Improving data flow
- 20:26Managing failures with Step Functions
- 22:11Learning from failures
- 24:23Closing and Q&A
related talks
39mBuilding Low-Code Applications with Serverless Workflows
20mModern Application Architecture with AWS Step Functions
28mThe Art of the State: Coordinating Services Using AWS Step Functions
23mOrchestration Lightning: Rapid-Fire AWS Step Functions Patterns
29mOrchestrating complex (not complicated) tasks using AWS serverless and Python
30mEvolving Serverless Architectures
41mGetting started with Orchestration and Choreography in Distributed Applications
25mOrchestrating Workflow for Microservices Integration