By Nicola Wright
Serverless computing enables DevOps teams to build applications without maintaining or managing servers in the cloud.
This enables teams to focus on developing new features and deploying new releases instead of worrying about infrastructure. It can also significantly reduce IT workloads in terms of server maintenance and management.
Amazon Web Services (AWS) offers multiple serverless options for compute, storage, databases, message queueing, and stream processing.
This post compares AWS Lambda, AWS Step Functions, and Lambda@Edge services in terms of pricing, use cases, and runtimes.
AWS Lambda is a serverless computing service offered by AWS. Developers can use Lambda to execute their code in the cloud. AWS Lambda uses Lambda functions to enable the use of the most popular coding languages.
You can run these functions independently of other code and output a result directly to users, other functions, or for consumption by other services. With Lambda, you only have to worry about your function and how output is used; the backend infrastructure is managed for you.
Similar to any serverless system, Lambda manages and provisions cloud infrastructure. Including servers, databases, backend, and security logic. You can build front-end applications without the complexities of physical hardware. The pricing of Lambda is based on the number of executions, and functions are offered as a service.
AWS Lambda use cases include:
Practical advice from AWS experts to help you weather the storm
With extensive insights, advice, and best practices from cloud leaders, our brand new white paper is the ultimate guide to optimizing your business with AWS.
Before getting started with AWS Lambda, let’s get to know its system components, execution models, and specs.
AWS Lambda components include:
Here is how AWS Lambda execution model works:
Here are some AWS Lambda specs you need to understand:
AWS Lambda@Edge is an extension of AWS Lambda that grants greater flexibility and lower latency to distributed Lambda functions. You can run Lambda@Edge functions with Node.js and Python.
The benefit of Lambda@Edge is that it uses the Amazon CloudFront content delivery network (CDN) to enable you to deliver function results globally. This is in contrast to Lambda, which requires you to provision instances in each location you want to operate from.
For example, imagine you are managing a serverless application in Chicago. With Lambda, a user in London would have to wait for a function request to travel all the way to your host server in the US and back.
To reduce this time, you would need to configure a mirror in Europe and manage two Lambda configurations.
With Lambda@Edge, you can manage your single configuration in the US and the CloudFront CDN automatically runs your function in the closest server to the user. This reduces latency without requiring additional management on your part.
There are many uses for Lambda@Edge processing. For example:
AWS Step Functions are designed to help DevOps teams manage multiple operations on AWS using a visual workflow editor. For example, you can create linked process steps with the output of one step becoming the input for the following step.
Step Functions translate your application development workflow into an easy-to-understand machine diagram. Step Functions automatically triggers and tracks each step of the process, and retries when there are errors.
You can use it to simplify complex workflows like machine learning model training, IT automation, and report generation.
AWS Step Functions is based on the concepts of state machines and tasks. These functions are used to pass state information from task to task once a defined event trigger is sent.
State machines represent the states you need to create in your process, the relationships of those states, and their input and output. For instance, you can create a state machine that coordinates each task in a workflow to improve customer experience. To create a state machine, you need to create a JSON template using the API or the AWS Console. The template must follow the Amazon States Language.
States are the individual elements of a state machine. Each state can make decisions based on the input, perform actions, and pass the output to other states. You can refer to a state by its name. The name must be a unique string within the scope of the entire state machine.
Tasks define how your states get their work done. Tasks can perform work through Lambda functions, by using an activity, or by passing parameters to the API of other services. These services include Simple Queue Service (SQS), Simple Notification Service (SNS), and DynamoDB.
An activity consists of program code that waits for an operator to perform an action or to provide input. You can host activities on Amazon EC2, Amazon ECS, or even on mobile devices.
Often, organizations want to scale applications according to their growing workloads, while paying less, and allowing different teams to work simultaneously on the app.
In the serverless model, you can achieve these goals by separating business logic into several decoupled services. A large serverless application can include a few hundred services.
The challenge comes when a large number of services need access to different parts of a shared state. In that case, you need to orchestrate the flow of data through all application services in a single place.
Step Functions help you handle all the data and state management necessary to keep serverless systems working effectively and at scale.
AWS Step Functions have several limits per workflow and per AWS account. You can change those limitations by submitting a limit increase request via the AWS support center. However, some limits can’t be changed:
AWS Step Functions enables you to automate many tasks, including:
AWS offers a free tier with some basic functionalities. Beyond the free tier, you are charged for the services you use, for as long as you use them.
The AWS free tier offers 4,000 Step Functions state transitions per month. In other tiers, Step Functions are billed at $0.025 per 1,000 state transitions. The charges of Step Functions come in addition to any AWS services you use.
The free tier includes one million requests per month, and 400,000 GB-seconds of compute time per month. The Lambda free tier is available permanently to both new and existing AWS customers, they don’t expire automatically.
The requests tier includes one million free requests per month. After you run out of free requests, this tier costs $0.20 per one million requests.
The duration tier comes with 3.2 million seconds of free computing time. After you run out of free computing time, tier costs $0.00001667 per every GB-second used.
There is no free tier for Lambda@Edge. You are billed for the total number of requests across all your functions. Request pricing is $0.60 per one million requests. Duration is calculated from the time you execute your code until it stops running or otherwise terminated.
You are billed $0.00005001 for every GB-second.
For example, if you allocate 256MB available memory per execution, then your duration charge will be $0.0128256 for every 256MB-second used.
All three services can help you reduce your IT workloads when used carefully. These services can help you automate tasks, optimize budgets, and significantly lighten the burden of managing hardware. However, AWS Lambda, AWS Step Function, and AWS Lambda@Edge have different use cases, pricing, and runtimes you need to consider.
Before deploying a serverless application in AWS, evaluate all your options and decide what service best suits your needs. The following guide can help you determine where to start.
|AWS Lambda||Lambda @Edge||Step Functions|
|Use cases||File processing, website hosting, mobile applications, data analytics||Security and privacy, dynamic web application, A/B testing, authentication and authorization, user prioritization||Media files transcoding, batch processing, publishing events from serverless workflows, managing container tasks, managing machine learning tasks|
|Supported runtimes||Node.js: 12, 10 Python 2.7 3.6, 3.7 and 3.8
Ruby 2.7, 2.5
.NET Core: 3.1, 2.1
Java 11, 8
|Node.js 10.x, 12.x
Python 3.7, 3.8
|Node.js 10.x, 12.x, Python 2.7, 3.6, 3.7 and 3.8
.NET 3.1, 2.1
|Execution unit||Lambda functions||Lambda @Edge functions||State Machine, Tasks, Lambda functions and triggers|
|Pricing||Free tier—one million requests per month
Requests tier—$0.20 per one million requests
Duration tier—$0.00001667 per every GB-second
|No free tier
$0.60 per one million requests
|Free tier—4,000 Step Functions state transitions per month
Beyond free tier— $0.025 per 1,000 state transitions
Einblicke in den AWS-Markt