AWS Lambda architecture brings serverless to enterprise cloud
A comprehensive collection of articles, videos and more, hand-picked by our editors
Coding for AWS Lambda can be slightly different than coding for traditional development languages. AWS Lambda supports...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Amazon Web Services (AWS) Lambda code creates threads and processes, but resources that AWS provisions -- memory and network bandwidth -- are shared among the threads and processes that are created. This can affect performance of the Lambda function.
AWS Lambda also relies on a "stateless" coding model, meaning the code cannot rely on the computing infrastructure that it runs on. For example, Lambda code cannot assume any particular hardware, system configuration, disk contents and so on. In addition, Lambda code should not be persistent if possible; persistent, or stateful data, must be stored in a cloud-compatible storage resource such as Amazon Simple Storage Service, a database like Amazon DynamoDB or another third-party online storage service. Lambda can access stateful data for later use.
There are several restrictions on activities within Lambda. For example, only TCP/IP sockets are available; TCP Port 25 activities, typically used for Simple Mail Transfer Protocol, are also limited to prevent misuse or malware attacks. Debugging system calls are also prohibited, preventing users from gaining access to the underlying Lambda infrastructure.
Lambda code is created using the console or can be packaged and uploaded as a compressed (zip) file. Include any libraries in the compressed package. If you don't want to use the Lambda console to create or upload functions, you could upload compressed packages through the Lambda command-line interface (CLI). The Lambda console and CLI allows developers to list, update and delete functions as needed.
Monitoring will report statistical data on AWS Lambda functions, including the total number of requests (invocations), errors, durations and throttled requests. Administrators can monitor AWS Lambda using the console, CLI, Amazon CloudWatch or APIs in the Lambda code that report to third-party monitoring tools.
AWS Lambda aims to shear time off cloud development
IT pros can avoid management overhead on AWS Lambda
How AWS Lambda pushes PaaS to next level
AWS Lambda to drive innovation in the cloud
Related Q&A from Stephen J. Bigelow
Cleanly divided and straightforward applications are good candidates for a container-based deployment, whereas complex applications pose more ...continue reading
Assessing the impact of containers on application workloads can be extremely challenging, partially because of how quickly containers are spun up and...continue reading
There are many tools that help with container orchestration, but it's important to review all the features before choosing a platform to make sure it...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.