Why Supabase is the open-source Firebase alternative

Introduction

Supabase is a tool that helps you build apps quickly by giving you ready-made backend services. It is open-source, which means anyone can see and change its code. This makes it a friendly and flexible choice compared to Firebase, which is closed and controlled by one company.

You want to build an app with a database, user login, and storage without writing all backend code.

You prefer using software that is open and can be customized or self-hosted.

You want to avoid vendor lock-in and keep control over your app's backend.

You need a backend that works well with SQL databases and real-time features.

You want a free or low-cost alternative to Firebase with similar features.

Syntax

Supabase

supabase start

# This command starts a local Supabase backend with database, authentication, and storage services.

Supabase uses PostgreSQL as its database, which is powerful and widely used.

You can interact with Supabase using simple APIs for authentication, database, and storage.

Examples

Starts the local Supabase backend services for development.

Supabase

supabase start

Logs you into your Supabase account to manage projects.

Supabase

supabase login

Initializes a new Supabase project in your current folder.

Supabase

supabase init

Sample Program

This example shows how to start Supabase locally, create a simple table for tasks, add a task, and then get the list of tasks. It demonstrates how Supabase uses a real SQL database you can control.

Supabase

# Start Supabase locally
supabase start

# Create a new table in the database
CREATE TABLE todos (
  id SERIAL PRIMARY KEY,
  task TEXT NOT NULL,
  completed BOOLEAN DEFAULT FALSE
);

# Insert a todo item
INSERT INTO todos (task) VALUES ('Learn Supabase');

# Query the todos
SELECT * FROM todos;

Important Notes

Supabase is built on open standards like PostgreSQL, making it easy to use and extend.

Because it is open-source, you can host Supabase yourself or use their cloud service.

Supabase provides real-time updates, authentication, and storage out of the box, similar to Firebase.

Summary

Supabase is an open-source backend platform that offers Firebase-like features.

It uses PostgreSQL, giving you a powerful and familiar database system.

Supabase is flexible, transparent, and helps you avoid vendor lock-in.

Practice

1. What is one main reason Supabase is considered an alternative to Firebase?

easy

A. It is open-source and uses PostgreSQL as its database.

B. It only supports NoSQL databases.

C. It requires proprietary software licenses.

D. It does not provide real-time features.

Solution

1. Step 1: Understand Supabase's core features

   Supabase is known for being open-source and using PostgreSQL, a popular SQL database.

2. Step 2: Compare with Firebase

   Firebase is proprietary and uses NoSQL, while Supabase offers an open-source alternative with SQL.

3. Final Answer:

   It is open-source and uses PostgreSQL as its database. -> Option A

4. Quick Check:

   Open-source + PostgreSQL = C [OK]

Hint: Remember Supabase is open-source with SQL, unlike Firebase [OK]

Common Mistakes:

• Thinking Supabase only supports NoSQL
• Assuming Supabase is proprietary
• Believing Supabase lacks real-time features

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

easy

A. const supabase = createSupabase('url', 'key');

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

C. const supabase = supabase.create('url', 'key');

D. const supabase = supabaseClient('url', 'key');

Solution

1. Step 1: Recall Supabase client initialization syntax

   The official method is using createClient with URL and key as arguments.

2. Step 2: Check each option

   Only const supabase = createClient('url', 'key'); uses the correct function name and syntax.

3. Final Answer:

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

4. Quick Check:

   createClient() is correct method [OK]

Hint: Look for createClient function with two string arguments [OK]

Common Mistakes:

• Using incorrect function names like supabaseClient or createSupabase
• Calling create as a method on supabase
• Mixing up argument order or missing quotes

3. Given this Supabase query in JavaScript:

const { data, error } = await supabase
  .from('users')
  .select('*')
  .eq('active', true);

What does data contain after execution?

medium

A. All users regardless of 'active' status.

B. An error object because the query is invalid.

C. All users where the 'active' field is true.

D. Only users where 'active' is false.

Solution

1. Step 1: Analyze the query filters

   The query selects all columns from 'users' where 'active' equals true.

2. Step 2: Understand the result

   The data variable holds the filtered list of users with active status true.

3. Final Answer:

   All users where the 'active' field is true. -> Option C

4. Quick Check:

   Filter .eq('active', true) returns active users [OK]

Hint: .eq('active', true) filters active users only [OK]

Common Mistakes:

• Assuming it returns all users without filtering
• Thinking it returns users with active false
• Believing the query causes an error

4. You wrote this Supabase query but get an error:

const { data, error } = await supabase
  .from('profiles')
  .select('id, name, email')
  .eq('verified', 'true');

What is the likely cause of the error?

medium

A. The 'verified' field is boolean but compared to string 'true'.

B. The table name 'profiles' is misspelled.

C. The select statement is missing parentheses.

D. Supabase does not support .eq() filters.

Solution

1. Step 1: Check data type mismatch in filter

   The query compares 'verified' boolean field to string 'true', causing type mismatch.

2. Step 2: Validate other parts

   Table name and select syntax are correct; .eq() is supported.

3. Final Answer:

   The 'verified' field is boolean but compared to string 'true'. -> Option A

4. Quick Check:

   Boolean compared to string causes error [OK]

Hint: Match filter value type to column type (boolean vs string) [OK]

Common Mistakes:

• Assuming .eq() is unsupported
• Thinking select needs parentheses
• Ignoring data type mismatch in filters

5. You want to avoid vendor lock-in by using Supabase instead of Firebase. Which feature of Supabase helps most with this?

hard

A. It stores data in a custom binary format.

B. It only works with proprietary cloud services.

C. It requires you to use Firebase SDKs.

D. It is open-source and uses a standard PostgreSQL database.

Solution

1. Step 1: Understand vendor lock-in

   Vendor lock-in happens when you depend on proprietary tech that is hard to move from.

2. Step 2: Identify Supabase's advantage

   Supabase is open-source and uses PostgreSQL, a widely supported standard database, easing migration.

3. Final Answer:

   It is open-source and uses a standard PostgreSQL database. -> Option D

4. Quick Check:

   Open-source + PostgreSQL = less lock-in [OK]

Hint: Open-source + standard DB = easy to switch later [OK]

Common Mistakes:

• Thinking Supabase requires Firebase SDKs
• Believing it uses proprietary cloud only
• Assuming data is stored in custom formats