Why serverless matters in AWS - Performance Analysis

Time Complexity: Why serverless matters

O(n)

Understanding Time Complexity

We want to see how the work needed changes when using serverless computing as more tasks come in.

How does the number of tasks affect the time it takes to handle them?

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

// AWS Lambda function triggered by events
// Each event runs one Lambda invocation
// Lambda scales automatically with events

for each event in events:
  invoke Lambda function(event)
    process event
    return result

This sequence shows how serverless functions handle each event separately and scale automatically.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Lambda function invocation for each event
• How many times: Once per event received

How Execution Grows With Input

Each new event causes one new Lambda invocation, so the work grows 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 operations grows linearly as events increase.

Final Time Complexity

Time Complexity: O(n)

This means the time to handle events grows directly in proportion to how many events arrive.

Common Mistake

[X] Wrong: "Serverless means all events are handled instantly with no increase in time."

[OK] Correct: Each event still needs its own processing time, so total time grows with more events, even if scaling is automatic.

Interview Connect

Understanding how serverless scales with workload shows you know how cloud services handle growing demand smoothly and efficiently.

Self-Check

"What if the Lambda function processes batches of events instead of one at a time? How would the time complexity change?"