⚑️ Step Functions - Express vs. Standard - What Are the Differences?


  • βŒ› Reading time: 11 minutes
  • πŸŽ“ Main Learning: Step Functions - Express vs. Standard
  • πŸ‘Ύ GitHub Code
  • ✍️ Blog Post

Hey Reader

while Sandro is learning something new at the AWS Community Day in Munich today, we'll explore Express and Standard Step Functions, the two types of workflows offered by AWS Step Functions.

We’ll break down their differences, when to use each, and the benefits of both.

If you want to try out Step Functions on your own, please check out our example repository which can be used to deploy both workflow types into your own AWS account.

Comparison Overview

Before we do a deep dive, here's a quick overview about the most important differences.

Standard Workflows

  • Max Duration: One year 🐌
  • Execution Start Rate: 800-1300/s
  • State Transition Rate: 800-5000/s
  • Pricing: By state transitions
  • Execution History: Detailed via APIs, console, and CloudWatch Logs
  • Execution Semantics: Exactly-once
  • Service Integrations: All supported
  • Distributed Map: βœ…
  • Activities: βœ…

Express Workflows

  • Max Duration: Five minutes ⚑️
  • Execution Start Rate: 6000/s
  • State Transition Rate: No limit
  • Pricing: By executions, duration, and memory
  • Execution History: Limited to 5 minutes
  • Execution Semantics: At-least-once (Async), At-most-once (Sync)
  • Service Integrations: All except Job-run (.sync) or Callback (.waitForTaskToken)
  • Distributed Map: ❌
  • Activities: ❌

It's very important to notice the billig differences:

  • ⏳ Duration at Express Step Functions vs.
  • πŸ”€ State Transitions at Standard Step Functions

Introduction

AWS Step Functions is a fully managed service that enables you to coordinate multiple AWS services (and basically everything else that has a HTTP API) into serverless workflows.

It simplifies building and running multi-step applications by providing a visual interface to design and manage workflows.

Key Features and Benefits

  1. Visual Workflow Design: Graphical interface for designing workflows.
  2. State Management: Automatically manages the state of each step.
  3. Error Handling: Built-in error handling capabilities.
  4. Integration with AWS Services: Seamless integration with AWS services.
  5. Scalability: Automatically scales to handle thousands of parallel executions.
  6. Cost Efficiency: Pay-as-you-go pricing.
  7. Audit and Monitoring: Detailed execution history and logs.
  8. Flexibility: Supports both Standard and Express workflows.

Standard Step Functions

Standard Workflows are designed for long-running, durable, and auditable state management. They guarantee exactly-once processing, ensuring each step is executed precisely one time.

Perfect for applications where data consistency and reliability are critical, such as financial transaction processing systems. They handle long-running processes that may span hours, days, or even months.

Standard Step Functions are durable, maintaining state and recovering from failures. They are also auditable, logging every step for review, which is crucial for compliance and debugging.

Express Step Functions

Express Workflows are designed for high-volume, short-duration, and cost-sensitive applications requiring fast state management. They are optimized for high-throughput and low-latency processing.

Express Workflows offer at-least-once processing, suitable for scenarios where occasional duplicate executions are acceptable. They are perfect for short-lived processes that complete within minutes and can handle thousands of executions per second.

Express Workflows are cost-effective, billed based on the number of requests and duration of each execution. They provide basic error handling and retry mechanisms, ensuring workflows can handle transient failures.

Choosing the Right Step Function

Choose Express Workflows for:

  • High-frequency
  • Short-duration tasks
  • Rapid execution
  • Tolerating transient errors

Opt for Standard Workflows for:

  • Long-running
  • Durable tasks
  • Detailed execution history
  • Robust error handling

Our Recommendation

Start with Express Step Functions unless you have a valid reason against it. They are cheaper and often sufficient. Remember to configure logging for Express Step Functions, as debugging can be slower on AWS’s side, but the cost reduction is often worth it.

Conclusion

AWS Step Functions offers Standard and Express workflows to meet different needs. Standard Workflows are ideal for long-running, complex tasks with robust error handling and detailed execution history. Express Workflows are perfect for high-throughput, short-duration tasks, offering rapid execution and cost efficiency.

Tobi & Sandro

our goal is to simplify AWS & Cloud Learning for everybody. You don't need expensive certifications to build on AWS!

Dr.-Otto-Bâßner-Weg 7a, Ottobrunn, Bavaria 85521 Β· Unsubscribe Β· Preferences​

AWS for the Real World

Join our community of over 9,300 readers delving into AWS. We highlight real-world best practices through easy-to-understand visualizations and one-pagers. Expect a fresh newsletter edition every two weeks.

Read more from AWS for the Real World

AWS FOR THE REAL WORLD ⏱️ Reading time: 8 minutes 🎯 Main Learning: Migrating from Edgio to CloudFront πŸ“ Blog Post πŸ’» GitHub Repository Hey Reader πŸ‘‹πŸ½After a busy week in Prague, both Tobi and I (Sandro) delivered our talks and we got quite some good feedback! We will share them in a separate newsletter soon.But this newsletter is all about accessing S3 within a VPC via Gateway endpoints vs. Internet routing. We know these networking issues are not the fanciest onces (looking at you AI) but...

Hey Reader πŸ‘‹πŸ½ We've been talking a lot about how great SST's switch to Pulumi was, and many of you have asked us how to use plain Pulumi directly. So today, we're sharing our quick guide to Pulumi - a tool we're really excited about since it lets us build infrastructure with languages we already know and love. No more learning weird syntax - just TypeScript, Python, or whatever we're comfortable with! We spent the last few days playing with it, and here's what we've learned... AWS Community...

Newsletter Header AWS FOR THE REAL WORLD ⏱️ Reading time: 8 minutes πŸŽ“ Main Learning: Migrating from Edgio to CloudFront ✍️ Blog Post πŸ’» GitHub Repository Hey Reader πŸ‘‹πŸ½ this newsletter is about πŸ₯ AI πŸ€– We haven't talked too much about AI, Bedrock, MCPs, and agents yet - so we want to change that. Please let us know if this it interests you to build AI on AWS, or if you are much more interested on hands-on fundamentals services. Should we focus on AI Services? Yes, I want to learn to build...