Why Edge Functions handle server-side logic in Supabase - Performance Analysis

Time Complexity: Why Edge Functions handle server-side logic

O(n)

Understanding Time Complexity

We want to understand how the work done by Edge Functions grows as we handle more requests or data.

How does the time to run server-side logic change when the input size changes?

Scenario Under Consideration

Analyze the time complexity of an Edge Function processing multiple database queries.

const { data, error } = await supabase
  .from('items')
  .select('*')
  .eq('user_id', userId)

for (const item of data) {
  await supabase
    .from('details')
    .select('*')
    .eq('item_id', item.id)
}
    

This code fetches items for a user, then for each item fetches its details.

Identify Repeating Operations

Look at the calls that happen multiple times.

• Primary operation: Database query inside the loop fetching details for each item.
• How many times: Once for each item returned in the first query.

How Execution Grows With Input

As the number of items grows, the number of detail queries grows too.

Input Size (n items)	Approx. API Calls/Operations
10	1 (items) + 10 (details) = 11
100	1 + 100 = 101
1000	1 + 1000 = 1001

Pattern observation: The total calls grow roughly in direct proportion to the number of items.

Final Time Complexity

Time Complexity: O(n)

This means the time grows linearly with the number of items processed.

Common Mistake

[X] Wrong: "The number of API calls stays the same no matter how many items there are."

[OK] Correct: Each item causes a separate query, so more items mean more calls.

Interview Connect

Understanding how server-side logic scales helps you design efficient cloud functions that handle growing data smoothly.

Self-Check

"What if we combined all detail queries into one batch call? How would the time complexity change?"

Practice

1. Why do Supabase Edge Functions run server-side logic close to users?

easy

A. To make apps faster and more secure by processing data near users

B. To store all user data permanently on the client device

C. To replace the need for any database in the app

D. To allow users to write code directly in the browser

Solution

1. Step 1: Understand the role of Edge Functions

   Edge Functions run code on servers close to users, reducing delay and improving security.

2. Step 2: Identify benefits of running logic near users

   This setup speeds up responses and keeps sensitive logic safe from client exposure.

3. Final Answer:

   To make apps faster and more secure by processing data near users -> Option A

4. Quick Check:

   Edge Functions = speed + security [OK]

Hint: Edge Functions run near users for speed and safety [OK]

Common Mistakes:

• Thinking Edge Functions store data on client devices
• Believing Edge Functions replace databases
• Assuming users write Edge Function code in browsers

2. Which is the correct way to define a simple Supabase Edge Function in JavaScript?

easy

A. async function handler() { console.log('Hello') }

B. function handler(req, res) { return 'Hello' }

C. export async function handler(req, res) { res.send('Hello') }

D. export default async function handler(req) { return 'Hello' }

Solution

1. Step 1: Recall Supabase Edge Function syntax

   Supabase Edge Functions export a default async function that receives a request and returns a response.

2. Step 2: Check each option's correctness

   export default async function handler(req) { return 'Hello' } correctly exports an async function with one parameter and returns a response. Others miss export default or proper response handling.

3. Final Answer:

   export default async function handler(req) { return 'Hello' } -> Option D

4. Quick Check:

   Default async export with req param = correct syntax [OK]

Hint: Edge Functions use 'export default async function(req)' [OK]

Common Mistakes:

• Missing 'export default' keyword
• Not using async function
• Incorrect function parameters

3. Given this Edge Function code snippet, what will be the response when called?

export default async function handler(req) {
  const user = { id: 1, name: 'Alice' };
  return new Response(JSON.stringify(user), { headers: { 'Content-Type': 'application/json' } });
}

medium

A. {"id":1,"name":"Alice"}

B. Error: user is not defined

C. undefined

D. Plain text response 'user'

Solution

1. Step 1: Analyze the function's return value

   The function returns a Response object with JSON string of the user object and proper content-type header.

2. Step 2: Determine the actual response content

   The JSON.stringify converts the user object to '{"id":1,"name":"Alice"}', which is sent as the response body.

3. Final Answer:

   {"id":1,"name":"Alice"} -> Option A

4. Quick Check:

   JSON.stringify(user) = JSON string response [OK]

Hint: JSON.stringify returns JSON text in response [OK]

Common Mistakes:

• Expecting raw object instead of JSON string
• Confusing variable scope errors
• Ignoring response headers

4. This Edge Function code throws an error when called. What is the problem?

export default async function handler(req) {
  const data = await fetch('https://api.example.com/data');
  return data.json();
}

medium

A. fetch URL is invalid syntax

B. Missing 'await' before data.json() causing a Promise to be returned

C. Function must not be async

D. Response must be a string, not JSON

Solution

1. Step 1: Identify async handling of fetch response

   fetch returns a Response object; calling data.json() returns a Promise that must be awaited.

2. Step 2: Spot missing 'await' before data.json()

   Without 'await', the function returns a Promise instead of resolved JSON, causing errors in response handling.

3. Final Answer:

   Missing 'await' before data.json() causing a Promise to be returned -> Option B

4. Quick Check:

   Await all async calls to get resolved data [OK]

Hint: Always await data.json() after fetch [OK]

Common Mistakes:

• Not awaiting JSON parsing
• Assuming fetch URL syntax error
• Thinking async keyword is wrong here

5. You want to keep user authentication logic secure and fast in your Supabase app. Why should you use Edge Functions for this instead of client-side code?

hard

A. Client-side code runs faster and is more secure than Edge Functions

B. Edge Functions store user passwords on the client device

C. Edge Functions run server-side, protecting secrets and reducing client load

D. Client-side code can access database directly without restrictions

Solution

1. Step 1: Understand security needs for authentication

   Authentication requires secret keys and sensitive logic that must not be exposed to users.

2. Step 2: Explain why Edge Functions are suitable

   Edge Functions run on the server close to users, keeping secrets safe and off the client, while improving response speed.

3. Step 3: Contrast with client-side code risks

   Client-side code is visible to users and cannot securely handle secrets or sensitive operations.

4. Final Answer:

   Edge Functions run server-side, protecting secrets and reducing client load -> Option C

5. Quick Check:

   Server-side = secure + fast auth logic [OK]

Hint: Keep secrets server-side with Edge Functions [OK]

Common Mistakes:

• Thinking client-side is more secure
• Believing Edge Functions expose passwords
• Assuming client code can safely access DB secrets