Lambda execution model in AWS - Time & Space Complexity

Time Complexity: Lambda execution model

O(n)

Understanding Time Complexity

When using AWS Lambda, it's important to understand how the time to handle requests grows as more requests come in.

We want to know how the number of Lambda executions changes when the number of incoming events increases.

Scenario Under Consideration

Analyze the time complexity of invoking Lambda functions for multiple events.

// Example: Processing multiple events with Lambda
for (const event of events) {
  const response = await lambda.invoke({
    FunctionName: 'MyFunction',
    Payload: JSON.stringify(event)
  }).promise();
  // process response
}
    

This code invokes a Lambda function once for each event in a list, processing them one by one.

Identify Repeating Operations

Look at what repeats as the input grows.

• Primary operation: Lambda function invocation API call
• How many times: Once per event in the input list

How Execution Grows With Input

Each new event causes one Lambda invocation, so the total calls grow directly with the number of events.

Input Size (n)	Approx. Api Calls/Operations
10	10 Lambda invocations
100	100 Lambda invocations
1000	1000 Lambda invocations

Pattern observation: The number of Lambda calls grows in a straight line with the number of events.

Final Time Complexity

Time Complexity: O(n)

This means the total Lambda invocations increase directly in proportion to the number of events.

Common Mistake

[X] Wrong: "Lambda can handle all events with just one invocation regardless of input size."

[OK] Correct: Each event usually triggers a separate Lambda invocation, so more events mean more calls, not just one.

Interview Connect

Understanding how Lambda scales with input helps you design systems that handle growing workloads smoothly and predict costs better.

Self-Check

"What if we batch multiple events into a single Lambda invocation? How would the time complexity change?"

Practice

1. What happens when an AWS Lambda function is not triggered by any event?

easy

A. The function does not run and no charges occur.

B. The function runs continuously in the background.

C. The function runs once every hour automatically.

D. The function runs only when manually started from the console.

Solution

1. Step 1: Understand Lambda's event-driven model

   A Lambda function runs only when triggered by an event, such as an API call or file upload.

2. Step 2: Consider billing and execution behavior

   If no event triggers the function, it does not execute and you are not charged.

3. Final Answer:

   The function does not run and no charges occur. -> Option A

4. Quick Check:

   Lambda runs only on events = C [OK]

Hint: Lambda runs only on events, no event means no run [OK]

Common Mistakes:

• Thinking Lambda runs continuously without events
• Assuming Lambda runs on a schedule by default
• Believing manual start is required for all executions

2. Which of the following is the correct way to define a Lambda handler function in Python?

easy

A. def handler(): print('Hello World')

B. function handler(event) { return 'Hello World'; }

C. handler(event, context) => { return 'Hello World'; }

D. def handler(event, context): return 'Hello World'

Solution

1. Step 1: Recall Python Lambda handler signature

   In Python, the handler must accept two parameters: event and context.

2. Step 2: Check syntax correctness

   def handler(event, context): return 'Hello World' correctly defines a Python function with event and context and returns a string.

3. Final Answer:

   def handler(event, context): return 'Hello World' -> Option D

4. Quick Check:

   Python handler(event, context) = A [OK]

Hint: Python Lambda handlers need event and context parameters [OK]

Common Mistakes:

• Using JavaScript syntax in Python handler
• Omitting context parameter
• Defining handler without parameters

3. Given this Python Lambda handler code:

def handler(event, context):
    return event['value'] * 2

What is the output if the event is {"value": 5}?

medium

A. Error: 'value' key missing

B. 5

C. 10

D. None

Solution

1. Step 1: Understand the handler logic

   The handler multiplies the 'value' from event by 2.

2. Step 2: Calculate output for event {'value': 5}

   5 * 2 = 10, so the function returns 10.

3. Final Answer:

   10 -> Option C

4. Quick Check:

   5 times 2 equals 10 [OK]

Hint: Multiply event['value'] by 2 for output [OK]

Common Mistakes:

• Confusing event keys or missing them
• Assuming function returns input unchanged
• Expecting error when key exists

4. This Lambda function code causes an error when triggered:

def handler(event, context):
    return event['data'] * 3

What is the likely cause?

medium

A. The function is missing the context parameter.

B. The event dictionary does not have the 'data' key.

C. The return statement syntax is incorrect.

D. Lambda functions cannot multiply values.

Solution

1. Step 1: Identify cause of error in code

   The function tries to access event['data'], which may not exist.

2. Step 2: Understand error from missing key

   If 'data' key is missing in event, a KeyError occurs causing the function to fail.

3. Final Answer:

   The event dictionary does not have the 'data' key. -> Option B

4. Quick Check:

   Missing event key causes error = B [OK]

Hint: Check if event keys exist before using them [OK]

Common Mistakes:

• Assuming context parameter missing causes error
• Thinking return syntax is wrong
• Believing Lambda cannot do arithmetic

5. You want your Lambda function to process multiple events concurrently without waiting for previous executions. Which Lambda feature supports this behavior?

hard

A. Automatic scaling with multiple concurrent executions

B. Manual start of multiple Lambda instances

C. Scheduled triggers to queue events

D. Using a single-threaded execution model

Solution

1. Step 1: Understand Lambda concurrency

   Lambda automatically scales by running multiple instances to handle events concurrently.

2. Step 2: Eliminate incorrect options

   Manual start and single-threaded models do not support concurrency; scheduled triggers queue events but don't scale automatically.

3. Final Answer:

   Automatic scaling with multiple concurrent executions -> Option A

4. Quick Check:

   Lambda auto-scales for concurrency = D [OK]

Hint: Lambda auto-scales to run many events at once [OK]

Common Mistakes:

• Thinking manual start is needed for concurrency
• Confusing scheduling with scaling
• Assuming Lambda runs single-threaded only