Understanding Amazon Step Functions and Exploring Different State Machines
What is Amazon Step Functions
AWS Step Functions is a serverless orchestration service designed to facilitate the integration of AWS Lambda functions and various other AWS services, enabling the development of mission-critical applications. Using the visual interface provided by Step Functions, you can visualize your application’s workflow as a sequence of event-triggered steps.
Step Functions operates on the principles of state machines and tasks. In this context, a workflow is referred to as a state machine, consisting of a sequence of event-triggered steps. Each individual step within the workflow is termed a state. A Task state denotes a discrete unit of work that can be executed by an AWS service, such as AWS Lambda, and can interact with any AWS service or API.
Step Functions comes equipped with built-in controls, allowing you to monitor the status of each step within your workflow to ensure that your application runs in the desired sequence and produces the expected outcomes. Depending on your specific requirements, you can configure Step Functions to invoke AWS services like Lambda to carry out various tasks. These workflows can be tailored to process and deploy machine learning models, control AWS services like AWS Glue to create extract, transform, and load (ETL) processes, or even establish long-running automated workflows for applications that necessitate human intervention.
State machine types
When configuring a state machine, you must make a crucial decision regarding its Type, which can be either Standard or Express. The default Type for state machines is Standard. A state machine designated as Standard is known as a “Standard workflow,” while one set as Express is referred to as an “Express workflow.”
The choice between Standard and Express Types significantly influences the behavior of your state machine executions, and this decision is permanent once the state machine is created.
Standard workflows are well-suited for tasks that require durability and auditability over extended periods, potentially up to one year. They are designed for processes where ensuring that tasks and states are executed…