Why Edge Functions handle server-side logic in Supabase - Visual Breakdown

Process Flow - Why Edge Functions handle server-side logic

Client sends request

↓

Edge Function receives request

↓

Edge Function runs server-side logic

↓

Edge Function accesses database or APIs

↓

Edge Function processes data

↓

Edge Function sends response back to client

The client sends a request that the Edge Function receives and runs server-side logic on. It can access databases or APIs, process data, and then send a response back to the client.

Execution Sample

Supabase

export default async function handler(req) {
  const { userId } = await req.json();
  const data = await fetchUserData(userId);
  return new Response(JSON.stringify(data));
}

This Edge Function receives a request with a user ID, fetches user data from the database, and returns it as a response.

Process Table

Step	Action	Input	Process	Output
1	Receive request	{"userId": "123"}	Parse JSON body	userId = "123"
2	Fetch data	userId = "123"	Query database for user 123	{"name": "Alice", "age": 30}
3	Prepare response	User data object	Convert to JSON string	{"name":"Alice","age":30}
4	Send response	JSON string	Send HTTP response to client	Response sent with user data

💡 Response sent back to client, Edge Function completes execution

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
req	undefined	{"userId":"123"}	{"userId":"123"}	{"userId":"123"}	{"userId":"123"}
userId	undefined	"123"	"123"	"123"	"123"
data	undefined	undefined	{"name":"Alice","age":30}	{"name":"Alice","age":30}	{"name":"Alice","age":30}
response	undefined	undefined	undefined	{"name":"Alice","age":30}	Sent to client

Key Moments - 3 Insights

Why does the Edge Function run server-side logic instead of the client?

Because the Edge Function can securely access databases and APIs that the client cannot, as shown in step 2 where it queries the database.

How does the Edge Function know which user data to fetch?

It reads the userId from the request body in step 1, which is sent by the client.

What happens after the Edge Function prepares the response?

It sends the response back to the client, ending the function execution as shown in step 4.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of userId after step 1?

A "Alice"

B undefined

C "123"

D null

💡 Hint

Check the 'userId' variable in the variable_tracker after step 1.

At which step does the Edge Function query the database?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Look at the 'Process' column in the execution_table for database query action.

If the client sends a different userId, how would the execution_table change?

A The Edge Function would skip step 2.

B The 'Input' in step 1 and 'Output' in step 2 would reflect the new userId and data.

C The response would be sent before fetching data.

D The function would not receive any request.

💡 Hint

Consider how input and output depend on the userId variable in the tables.

Concept Snapshot

Edge Functions run server-side logic close to users.
They securely access databases and APIs.
They receive client requests, process data, and send responses.
This keeps sensitive logic off the client.
Edge Functions improve performance and security.

Full Transcript

Edge Functions handle server-side logic by receiving requests from clients, running code on the server, accessing databases or APIs securely, processing data, and sending responses back. This flow ensures sensitive operations happen safely on the server, not on the user's device. The example shows an Edge Function receiving a user ID, fetching user data, and returning it. Variables like userId and data change step-by-step as the function runs. Key moments include understanding why logic runs server-side, how input is read, and when the response is sent. Quizzes test knowledge of variable values and execution steps.

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