Why Edge Functions handle server-side logic in Supabase

Introduction

Edge Functions run code close to users to handle tasks securely and quickly on the server side.

When you want to keep sensitive data safe and not expose it to users.

When you need to process data or make decisions before sending results to the user.

When you want faster responses by running code near the user's location.

When you want to reduce load on your main servers by offloading tasks.

When you need to customize responses based on user location or device.

Syntax

Supabase

import { serve } from "https://deno.land/std@0.168.0/http/server.ts";

serve((request) => {
  // Your server-side logic here
  return new Response('Hello from Edge Function');
});

Edge Functions use simple JavaScript or TypeScript to run server-side code.

They respond to HTTP requests and can access secure resources.

Examples

A basic Edge Function that returns a simple greeting.

Supabase

import { serve } from "https://deno.land/std@0.168.0/http/server.ts";

serve((request) => {
  return new Response('Hello World');
});

This Edge Function fetches data from another API and returns it as JSON.

Supabase

import { serve } from "https://deno.land/std@0.168.0/http/server.ts";

serve(async (request) => {
  const data = await fetch('https://api.example.com/data');
  const json = await data.json();
  return new Response(JSON.stringify(json), { headers: { 'Content-Type': 'application/json' } });
});

Sample Program

This Edge Function simulates server-side logic by creating a user object and returning a personalized greeting.

Supabase

import { serve } from "https://deno.land/std@0.168.0/http/server.ts";

serve((request) => {
  const user = { id: 1, name: 'Alice' };
  // Simulate server-side logic like authentication or data fetching
  const message = `Hello, ${user.name}! This message is from the server.`;
  return new Response(message, { headers: { 'Content-Type': 'text/plain' } });
});

Important Notes

Edge Functions run outside the user's browser, so they keep secrets safe.

They help make apps faster by running code near the user.

Always keep your server-side logic in Edge Functions to protect data and improve performance.

Summary

Edge Functions run server-side code close to users for speed and security.

They handle tasks like data processing, authentication, and API calls.

Using Edge Functions helps keep sensitive logic safe and apps responsive.

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