# Step Functions
### **Problems with Lambda**
π **In simple terms:**\
Step Functions help you connect multiple serverless functions/services into a workflow, step by step, with logic and rules.
𧩠How it works
* You define a workflow (a state machine).
* Each step can be a task (like running a Lambda), a decision (if/else), or a wait/retry.
* AWS Step Functions manage the order, handle errors/retries, and keep track of the state.
Imagine you run an online shoe shop π.\
When a customer places an order:
1. Step 1 β Check payment (Lambda).
2. Step 2 β If payment succeeds β reserve inventory (DynamoDB).
3. Step 3 β If inventory is available β arrange shipping (another Lambda).
4. Step 4 β Send confirmation email (SNS).
5. If something fails β Step Functions can retry, send alerts, or stop.
β‘ Instead of you writing all this logic manually, Step Functions handle the flow.
π **Analogy**
Think of Step Functions like a project manager:
* Assigns tasks in order.
* Makes decisions if something goes wrong.
* Keeps track of progress.
* Ensures nothing is missed.
### π οΈ **Two types of workflow**
1. Standard Workflows β Long-running (can last days).
Designed for long-running, reliable processes.
* Duration: Can run for up to 1 year.
* Executions: Millions of executions per month.
* Execution history: Stored for up to 90 days (you can see every step).
* Pricing: Pay per state transition.
* Best for:
* Order processing
* Payment workflows
* Fraud checks
* Any process that must be durable and auditable.
π Example:\
A loan application process that takes days/weeks β Step Functions Standard keeps track of the workflow until it finishes.
2. Express Workflows β Fast, high-volume (run in milliseconds, millions of executions).
* Designed for high-volume, short-duration processes.
* Duration: Up to 5 minutes.
* Executions: Millions per second (very high throughput).
* Execution history: Short-lived, logs go to CloudWatch or X-Ray.
* Pricing: Pay for execution duration + number of requests (cheaper at scale).
* Best for:
* Real-time data processing
* IoT event handling
* Streaming data (video/audio)
* High-volume API requests
π Example:\
A real-time image recognition app where thousands of users upload pictures every second β Express workflows process each quickly and cheaply.
**Comparison Table**
| Feature | Standard Workflow ποΈ | Express Workflow β‘ |
| --------------------- | --------------------------------- | --------------------------------- |
| **Max duration** | 1 year | 5 minutes |
| **Execution rate** | Thousands/sec | Millions/sec |
| **Execution history** | 90 days | Sent to CloudWatch/X-Ray |
| **Cost model** | Per state transition | Per execution + duration |
| **Use case** | Long-running, auditable processes | High-volume, real-time processing |
### **Components of Step Functions**
1\. State Machine ποΈ
* The overall workflow definition.
* Itβs like a map showing each step, order, and rules.
* Written in Amazon States Language (ASL) (JSON format).
2\. States π
Each step in your workflow is called a state.\
There are different types:
* Task β Runs work (like a Lambda, ECS job, Glue job).
* Choice β If/Else branching (decision-making).
* Parallel β Runs multiple branches at the same time.
* Map β Runs the same step for multiple items (looping).
* Wait β Pause for a certain time.
* Pass β Passes input to output without doing anything.
* Fail / Succeed β Ends the workflow with failure/success.
3\. Transitions π
* Define how the workflow moves from one state to the next.
* Example: βAfter Task 1 β go to Task 2β OR βIf error β retry or go to Fail state.β
4\. Input & Output (State Data) π¦
* Each state can receive input and produce output.
* Step Functions pass this data along the workflow.
* Example: Payment check β returns βapproved/deniedβ β next step uses that info.
5\. Error Handling & Retries β οΈ
* Built-in system to retry failed steps, catch errors, and move to backup steps.
* Example: If payment system fails β retry 3 times β if still fails β send alert.
6\. Execution βΆοΈ
* Each run of the workflow is called an execution.
* You can track the status (running, succeeded, failed)
π Analogy
Think of Step Functions like a recipe book:
* State Machine = the whole recipe.
* States = individual steps (chop, cook, mix).
* Transitions = what comes after chopping (cook).
* Error Handling = if food burns, try again or order pizza π.
* Execution = each time you cook following the recipe.
**States**
