AWS Step Functions
What is it?
AWS Step Functions is a service for coordinating multiple AWS services into visual, reliable workflows made of defined steps.
Explain like I'm 5
Why was it created?
Coordinating many serverless steps with custom code is fragile and hard to track. Step Functions was created to orchestrate them reliably as a managed state machine.
Where is it used?
- Orchestrating serverless workflows
- Coordinating Lambda functions
- Long-running or multi-step processes
- Error handling and retries across steps
Why should developers care?
It's AWS's main tool for serverless workflow orchestration, useful whenever a task spans several services or steps.
How does it work?
You define a state machine — a series of steps with logic for sequencing, branching, parallelism, retries, and error handling. Step Functions runs it, calling services like Lambda at each step, tracking state and progress, and handling failures per your rules.
Real-world example
An order workflow runs steps in order: validate payment, reserve inventory, then ship — with automatic retries and a defined path if any step fails.
Common use cases
- Multi-step serverless workflows
- Coordinating several Lambdas
- Built-in retries and error handling
- Long-running business processes
Advantages
- Reliable step coordination
- Built-in retries and error handling
- Visual workflow representation
- Tracks state across steps
Disadvantages
- AWS-specific
- State-machine definition learning curve
- Cost at high step volumes
- Overkill for simple, single-step tasks
When should you use it?
When a process spans multiple steps or services and needs reliable sequencing, retries, and error handling.
When should you avoid it?
For a single function or a simple linear call where orchestration adds needless overhead.
Alternatives
Related terms
Interview questions
Beginner
- What do Step Functions do?
- What is a state machine here?
Intermediate
- How does it handle retries and errors?
- How does it coordinate Lambdas?
Senior
- When would you use Step Functions over event-driven choreography?
- How do you design long-running workflows reliably?
Common misconceptions
- "Step Functions run your business logic" — they orchestrate steps and call services like Lambda that do the work.
- "It's just a fancy queue" — it's a stateful workflow engine with branching, parallelism, and error handling.
Fun facts
- Workflows are defined as state machines and can be viewed as a visual diagram.
- It can wait, branch, run steps in parallel, and retry — all without custom orchestration code.
Timeline
- 2016 — AWS Step Functions launches
Learning resources
Quick summary
AWS Step Functions orchestrates multi-step serverless workflows as reliable state machines, coordinating services like Lambda with built-in retries and branching.
Cheat sheet
- Serverless workflow orchestration
- Defined as a state machine
- Branching, parallelism, retries
- Coordinates Lambdas and services