Why server-side logic reduces client complexity in Supabase - Performance Analysis

Time Complexity: Why server-side logic reduces client complexity

O(n)

Understanding Time Complexity

We want to see how moving logic to the server changes how much work the client does.

How does this affect the number of operations the client must perform?

Scenario Under Consideration

Analyze the time complexity of client vs server logic in Supabase.

// Client fetches all items and filters locally
const { data, error } = await supabase
  .from('items')
  .select('*')

const filtered = data.filter(item => item.category === 'books')

// Server filters items before sending
const { data: filteredData, error: filteredError } = await supabase
  .from('items')
  .select('*')
  .eq('category', 'books')

The first fetch gets all data and filters on client; the second fetch filters on server.

Identify Repeating Operations

• Primary operation: Fetching data rows from the database.
• How many times: Once per query, but amount of data fetched varies.
• Client filtering: Happens for every item received.
• Server filtering: Happens once inside the database engine.

How Execution Grows With Input

As the number of items grows, client filtering work grows with all items fetched.

Input Size (n)	Approx. Client Filtering Operations
10	10 filter checks
100	100 filter checks
1000	1000 filter checks

With server filtering, client only processes filtered results, so work stays smaller.

Final Time Complexity

Time Complexity: O(n)

This means client work grows linearly with data size when filtering client-side.

Common Mistake

[X] Wrong: "Fetching all data and filtering on client is just as fast as server filtering."

[OK] Correct: Client must handle every item, so work grows with total data size, causing slower response and more data transfer.

Interview Connect

Understanding where to place logic helps you design systems that keep clients fast and responsive, a key skill in cloud development.

Self-Check

"What if the server filters data but also paginates results? How would that affect the time complexity on the client?"

Practice

1. Why does moving logic to the server reduce complexity on the client side in Supabase?

easy

A. Because the client does not need to handle complex rules or validations.

B. Because the client can store all data locally without syncing.

C. Because the client runs faster without any network calls.

D. Because the client can directly modify the database schema.

Solution

1. Step 1: Understand client responsibilities

   The client usually handles user interface and simple logic but complex rules can make it bulky.

2. Step 2: Role of server-side logic

   Moving complex rules to the server means the client only sends requests and receives results, simplifying its code.

3. Final Answer:

   Because the client does not need to handle complex rules or validations. -> Option A

4. Quick Check:

   Server logic reduces client complexity = A [OK]

Hint: Server logic handles rules, client stays simple [OK]

Common Mistakes:

• Thinking client stores all data locally
• Assuming client runs faster without network
• Believing client can change database schema

2. Which of the following is the correct way to define a PostgreSQL function in Supabase for server-side logic?

easy

A. CREATE FUNCTION check_user() RETURNS void AS $$ BEGIN IF NEW.age < 18 THEN RAISE EXCEPTION 'Too young'; END IF; END; $$ LANGUAGE plpgsql;

B. CREATE FUNCTION check_user RETURNS void BEGIN IF NEW.age < 18 THEN RAISE EXCEPTION 'Too young'; END IF; END;

C. FUNCTION check_user() RETURNS void { IF NEW.age < 18 THEN THROW 'Too young'; }

D. CREATE PROCEDURE check_user() BEGIN IF NEW.age < 18 THEN RAISE ERROR 'Too young'; END IF; END;

Solution

1. Step 1: Check PostgreSQL function syntax

   PostgreSQL functions use CREATE FUNCTION, specify RETURNS, and use $$ to wrap the body with LANGUAGE plpgsql.

2. Step 2: Identify correct syntax in options

   CREATE FUNCTION check_user() RETURNS void AS $$ BEGIN IF NEW.age < 18 THEN RAISE EXCEPTION 'Too young'; END IF; END; $$ LANGUAGE plpgsql; correctly uses CREATE FUNCTION, RETURNS void, $$ body $$, and LANGUAGE plpgsql.

3. Final Answer:

   CREATE FUNCTION check_user() RETURNS void AS $$ BEGIN IF NEW.age < 18 THEN RAISE EXCEPTION 'Too young'; END IF; END; $$ LANGUAGE plpgsql; -> Option A

4. Quick Check:

   Correct PostgreSQL function syntax = D [OK]

Hint: Look for CREATE FUNCTION with $$ and LANGUAGE plpgsql [OK]

Common Mistakes:

• Omitting RETURNS keyword
• Missing $$ around function body
• Using THROW or RAISE ERROR instead of RAISE EXCEPTION

3. Given this Supabase trigger function, what happens when a new user with age 16 is inserted?

CREATE FUNCTION check_age() RETURNS trigger AS $$ BEGIN IF NEW.age < 18 THEN RAISE EXCEPTION 'User too young'; END IF; RETURN NEW; END; $$ LANGUAGE plpgsql; CREATE TRIGGER age_check BEFORE INSERT ON users FOR EACH ROW EXECUTE FUNCTION check_age();

medium

A. The insert succeeds and the user is added.

B. The insert succeeds but age is set to 18 automatically.

C. The insert fails with an error 'User too young'.

D. The insert is ignored silently without error.

Solution

1. Step 1: Understand trigger behavior

   The trigger runs BEFORE INSERT and checks if NEW.age is less than 18.

2. Step 2: Analyze condition for age 16

   Since 16 < 18, the trigger raises an exception 'User too young', which stops the insert.

3. Final Answer:

   The insert fails with an error 'User too young'. -> Option C

4. Quick Check:

   Trigger raises error on age < 18 = C [OK]

Hint: Trigger raises error if condition met, blocking insert [OK]

Common Mistakes:

• Thinking insert succeeds despite error
• Assuming age auto-corrects to 18
• Believing insert is ignored without error

4. You wrote this trigger function in Supabase but it does not block invalid inserts as expected:

CREATE FUNCTION check_age() RETURNS trigger AS $$ BEGIN IF NEW.age < 18 THEN RETURN NULL; END IF; RETURN NEW; END; $$ LANGUAGE plpgsql;

What is the main issue?

medium

A. The function must return OLD instead of NEW.

B. Returning NULL in BEFORE INSERT triggers causes the row to be skipped silently.

C. The trigger is missing the EXECUTE FUNCTION statement.

D. The function should use RAISE EXCEPTION to block inserts, not RETURN NULL.

Solution

1. Step 1: Understand RETURN NULL in triggers

   In BEFORE INSERT triggers, returning NULL silently skips the row without error.

2. Step 2: Correct way to block insert

   To block inserts with an error, the function must RAISE EXCEPTION instead of returning NULL.

3. Final Answer:

   The function should use RAISE EXCEPTION to block inserts, not RETURN NULL. -> Option D

4. Quick Check:

   Use RAISE EXCEPTION to block inserts = A [OK]

Hint: RETURN NULL skips silently; use RAISE EXCEPTION to block [OK]

Common Mistakes:

• Returning NULL expecting error
• Forgetting EXECUTE FUNCTION in trigger
• Returning OLD in insert triggers

5. You want to reduce client complexity by enforcing a rule that users must have unique emails and be at least 18 years old. Which combination of Supabase features best achieves this with minimal client code?

hard

A. Check email uniqueness and age on the client before sending data to Supabase.

B. Use a UNIQUE constraint on email and a BEFORE INSERT trigger function that raises an exception if age < 18.

C. Use a BEFORE INSERT trigger to check email uniqueness and age, but no database constraints.

D. Use only a UNIQUE constraint on email and let the client check age.

Solution

1. Step 1: Enforce email uniqueness

   A UNIQUE constraint on the email column ensures no duplicates at the database level.

2. Step 2: Enforce age rule server-side

   A BEFORE INSERT trigger function can check age and raise an exception if under 18, blocking invalid inserts.

3. Final Answer:

   Use a UNIQUE constraint on email and a BEFORE INSERT trigger function that raises an exception if age < 18. -> Option B

4. Quick Check:

   Database constraints + trigger enforce rules, reduce client code = B [OK]

Hint: Combine UNIQUE constraint and trigger for full server-side checks [OK]

Common Mistakes:

• Relying only on client-side checks
• Using triggers without constraints for uniqueness
• Ignoring age validation on server