AWS Lambda Serverless Computing

# CHAPTER 15

AWS Lambda Serverless Computing #

1. Introduction #

2. Learning Objectives #

• Define "Serverless Computing".

• Understand how AWS Lambda executes code in response to Events.

• Identify common triggers for Lambda functions.

• Understand the Lambda pricing model (paying by the millisecond).

• Create and execute a simple Lambda function in the AWS Console.

3. Beginner-Friendly Explanation #

• EC2 (Traditional): You hire a taxi driver for the whole day. Even if you stay inside a mall for 5 hours, the taxi waits outside, the engine runs, and you pay him by the hour.

• Lambda (Serverless): You step outside the mall and snap your fingers. A chauffeur instantly teleports into existence, drives you to your destination, drops you off, and instantly vanishes. You are billed precisely for the 4 minutes and 12 seconds the drive took. If you don't snap your fingers for a month, your bill is $0.00.

AWS Lambda functions are invisible snippets of code that sleep until an Event wakes them up. They execute their logic, and then instantly vanish.

4. Event-Driven Architecture #

Common Triggers:

• Amazon S3: A user uploads a high-resolution photo to an S3 bucket. This "upload event" instantly triggers a Lambda function that compresses the photo and saves it back to S3.

• API Gateway: A user visits a website and requests data. API Gateway catches the HTTP request and triggers a Lambda function to fetch data from DynamoDB.

• EventBridge (Cron): A timer triggers the Lambda function every day at midnight to run an automated database backup script.

5. Supported Languages #

• Node.js (JavaScript/TypeScript)

• Python

• Java

• Go

• C# / .NET

• Ruby

6. The Pricing Model (Micro-Billing) #

7. Mini Project: Create a Lambda Function #

Step-by-Step Tutorial:

1. 1. Open the AWS Console and search for Lambda.

1. 2. Click Create function.

1. 3. Select Author from scratch.

1. 4. Function name: HelloCloudFunction.

1. 5. Runtime: Select Python 3.12.

1. 6. Click Create function.

1. 7. Scroll down to the Code source editor. You will see a default lambda_handler function. Replace it with this code:

import json

def lambda_handler(event, context):
    # 'event' contains the data passed to the function
    user_name = event.get('name', 'Cloud Explorer')
    
    greeting = f"Hello, {user_name}! Your Serverless code is running!"
    
    return {
        'statusCode': 200,
        'body': json.dumps(greeting)
    }

1. 8. Click Deploy to save the code.

1. 9. Click the Test button. Name the test event Test1.

1. 10. In the Event JSON box, enter: {"name": "Alice"}. Save it.

1. 11. Click Test again.

1. 12. Look at the Execution Results! You will see the successful response: "Hello, Alice! Your Serverless code is running!" Notice the "Billed Duration" is likely under 2 milliseconds!

8. Best Practices #

• Stateless Design: Lambda functions are fundamentally stateless. If Function Execution #1 saves a temporary file to local disk, Function Execution #2 will likely run on a completely different invisible server and cannot see that file. Any persistent data MUST be saved to an external database (like DynamoDB) or S3.

9. Common Mistakes #

• The Cold Start Problem: If a Lambda function hasn't been triggered in 15 minutes, AWS puts it in "deep sleep." When a user triggers it, AWS has to fetch the code, provision a micro-container, and boot the runtime environment. This can cause the first execution to take 1 or 2 seconds (a "Cold Start"). All subsequent executions happen in milliseconds. (If 1 second of lag is unacceptable for your architecture, you must use "Provisioned Concurrency" to keep functions warm).

10. Exercises #

1. 1. Define the pricing model of AWS Lambda compared to Amazon EC2.

1. 2. List three AWS services that can act as "Triggers" to execute a Lambda function.

11. MCQs with Answers #

12. Interview Questions #

• Q: Explain the concept of "Serverless" computing. Does serverless mean there are no servers physically involved?

• Q: Describe the "Cold Start" phenomenon in AWS Lambda. How does it impact application latency, and what architectures are most sensitive to it?

13. FAQs #

14. Summary #

15. Next Chapter Recommendation #