Supabase architecture (Postgres, Auth, Storage, Realtime, Edge Functions) - Time & Space Complexity

Time Complexity: Supabase architecture (Postgres, Auth, Storage, Realtime, Edge Functions)

O(n)

Understanding Time Complexity

We want to understand how the work done by Supabase services grows as more users or data are involved.

How does the number of operations change when we use Postgres, Auth, Storage, Realtime, and Edge Functions together?

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

// User signs up
const { data, error } = await supabase.auth.signUp({ email, password })

// User uploads a file
const { data: fileData, error: fileError } = await supabase.storage
  .from('avatars')
  .upload('public/avatar1.png', file)

// User fetches messages in realtime
const subscription = supabase
  .from('messages')
  .on('INSERT', payload => console.log('New message:', payload))
  .subscribe()

// User calls an edge function
const response = await supabase.functions.invoke('hello-world')

This sequence shows a user signing up, uploading a file, listening for new messages, and calling a serverless function.

Identify Repeating Operations

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

• Primary operation: API calls to Supabase services (Auth, Storage, Realtime, Edge Functions)
• How many times: Each user action triggers one or more calls; Realtime subscription listens continuously for new events

How Execution Grows With Input

As more users sign up and upload files, the number of API calls grows roughly with the number of users.

Input Size (n users)	Approx. Api Calls/Operations
10	~10 sign-ups + 10 uploads + 10 edge calls + ongoing realtime events
100	~100 sign-ups + 100 uploads + 100 edge calls + ongoing realtime events
1000	~1000 sign-ups + 1000 uploads + 1000 edge calls + ongoing realtime events

Pattern observation: The number of operations grows linearly with the number of users and their actions.

Final Time Complexity

Time Complexity: O(n)

This means the total work grows directly in proportion to the number of users and their actions.

Common Mistake

[X] Wrong: "Realtime subscriptions cause the system to do the same work regardless of user count."

[OK] Correct: Each active subscription listens and processes events, so more users mean more ongoing work.

Interview Connect

Understanding how service calls grow with users helps you design scalable apps and explain your architecture choices clearly.

Self-Check

"What if we batch user uploads instead of uploading one file at a time? How would the time complexity change?"

Practice

1. Which Supabase component is responsible for managing user sign-ups and logins?

easy

A. Storage

B. Postgres

C. Realtime

D. Auth

Solution

1. Step 1: Understand Supabase components

   Supabase has several parts: Postgres for data, Auth for users, Storage for files, Realtime for live updates, and Edge Functions for custom code.

2. Step 2: Identify user management part

   The component that handles user sign-ups, logins, and authentication is called Auth.

3. Final Answer:

   Auth -> Option D

4. Quick Check:

   User management = Auth [OK]

Hint: Auth means user login and signup system [OK]

Common Mistakes:

• Confusing Postgres with user management
• Thinking Storage handles users
• Mixing Realtime with authentication

2. Which of the following is the correct way to initialize Supabase client in JavaScript?

easy

A. const supabase = Supabase.create('url', 'anon_key');

B. const supabase = createClient('url', 'anon_key');

C. const supabase = supabaseClient('url', 'anon_key');

D. const supabase = new Supabase('url', 'anon_key');

Solution

1. Step 1: Recall Supabase client initialization syntax

   Supabase uses the function createClient(url, key) to create a client instance.

2. Step 2: Match correct syntax

   const supabase = createClient('url', 'anon_key'); matches the exact syntax: const supabase = createClient('url', 'anon_key');

3. Final Answer:

   const supabase = createClient('url', 'anon_key'); -> Option B

4. Quick Check:

   Use createClient() to initialize Supabase [OK]

Hint: Use createClient() function to start Supabase [OK]

Common Mistakes:

• Using new keyword with Supabase
• Calling wrong function names
• Mixing class and function syntax

3. Given this code snippet, what will be logged if a new row is inserted into the 'messages' table?

const subscription = supabase
  .from('messages')
  .on('INSERT', payload => {
    console.log('New message:', payload.new.text);
  })
  .subscribe();

medium

A. New message: [text of inserted row]

B. New message: undefined

C. Error: .subscribe() is not a function

D. No output, subscription does not listen to INSERT

Solution

1. Step 1: Understand Realtime subscription

   The code listens for INSERT events on the 'messages' table and logs the new row's text field.

2. Step 2: Analyze the callback behavior

   When a new row is inserted, payload.new contains the new row data, so payload.new.text is the inserted message text.

3. Final Answer:

   New message: [text of inserted row] -> Option A

4. Quick Check:

   Realtime INSERT event logs new row text [OK]

Hint: INSERT event payload.new has new row data [OK]

Common Mistakes:

• Expecting payload.old instead of payload.new
• Thinking .subscribe() is invalid
• Assuming no output on INSERT

4. You wrote this Edge Function to upload a file to Supabase Storage but it fails with a permission error. What is the likely cause?

export async function POST(request) {
  const supabase = createClient(SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY);
  const data = await request.formData();
  const file = data.get('file');
  const { error } = await supabase.storage.from('avatars').upload(file.name, file);
  if (error) return new Response(error.message, { status: 400 });
  return new Response('Upload successful');
}

medium

A. Storage upload requires user session, missing auth

B. The 'avatars' bucket does not exist

C. File object is not properly extracted from formData

D. Using SERVICE_ROLE_KEY in Edge Function is insecure and disabled

Solution

1. Step 1: Check authentication context for storage upload

   Storage upload requires a user session or proper auth context; using service role key alone in Edge Functions does not provide user session.

2. Step 2: Identify missing user session

   Without user session, storage upload is denied due to permission error.

3. Final Answer:

   Storage upload requires user session, missing auth -> Option A

4. Quick Check:

   Storage upload needs user auth session [OK]

Hint: Storage upload needs user session, not just service key [OK]

Common Mistakes:

• Assuming service role key works for storage upload
• Ignoring bucket existence
• Not checking file extraction from formData

5. You want to build a chat app using Supabase that updates messages live and stores user avatars. Which combination of Supabase components should you use?

hard

A. Auth for messages, Edge Functions for avatars, Storage for live updates

B. Realtime for messages and avatars, Postgres for user login

C. Postgres for messages, Storage for avatars, Realtime for live updates, Auth for user login

D. Storage for messages, Postgres for avatars, Edge Functions for live updates

Solution

1. Step 1: Identify storage needs

   Messages are structured data best stored in Postgres; avatars are files stored in Storage.

2. Step 2: Identify live update and user management

   Realtime provides live updates for messages; Auth manages user login.

3. Final Answer:

   Postgres for messages, Storage for avatars, Realtime for live updates, Auth for user login -> Option C

4. Quick Check:

   Use Postgres, Storage, Realtime, Auth together [OK]

Hint: Messages in Postgres, avatars in Storage, live with Realtime [OK]

Common Mistakes:

• Mixing Storage with live updates
• Using Realtime for file storage
• Confusing Auth with data storage