Invoking Edge Functions from client in Supabase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an Edge Function in Supabase?

An Edge Function in Supabase is a small piece of code that runs close to the user, on the network edge, to respond quickly to client requests.

beginner

How do you call an Edge Function from a client application in Supabase?

You call an Edge Function by using the Supabase client library's `functions.invoke` method with the function's name and optional parameters.

intermediate

Why use Edge Functions instead of calling the database directly from the client?

Edge Functions add a security layer, allow custom logic, and reduce latency by running code near the user instead of exposing the database directly.

beginner

What is the typical response format when invoking an Edge Function from the client?

The response is usually a JSON object containing the data or result returned by the Edge Function, which the client can then use.

intermediate

What should you consider about authentication when invoking Edge Functions from the client?

You should ensure the client is authenticated if the function requires it, often by passing the user's access token in the request headers.

Which Supabase client method is used to call an Edge Function?

A functions.invoke

B database.query

C auth.signIn

D storage.upload

The correct method to call an Edge Function is functions.invoke.

Where do Edge Functions run in relation to the user?

A Only on the database server

B In the cloud data center far away

C On the user's device

D On the network edge close to the user

Edge Functions run on the network edge, close to the user, to reduce latency.

What is a key benefit of using Edge Functions for client requests?

A They increase database load

B They expose database credentials

C They improve security and reduce latency

D They require no authentication

Edge Functions improve security by hiding database details and reduce latency by running near the user.

What format does the client usually receive from an Edge Function?

A JSON object

B Binary data

C HTML page

D Plain text only

Edge Functions typically return JSON objects for easy use in client applications.

How should authentication tokens be handled when calling Edge Functions?

A Never send tokens

B Send tokens in request headers if required

C Embed tokens in URL query parameters

D Tokens are not needed for Edge Functions

Tokens should be sent securely in request headers when the function requires authentication.

Explain how to invoke an Edge Function from a Supabase client and why it is useful.

Think about how client talks to backend code near the user.

Describe the role of authentication when calling Edge Functions from the client.

Consider how to keep your backend safe from strangers.