Why serverless functions extend Firebase - Why It Works

Introduction

Firebase provides tools to build apps quickly, but sometimes you need custom backend code. Serverless functions let you run code on demand without managing servers, extending Firebase's capabilities easily.

When you want to run custom code triggered by database changes without managing a server.

When you need to handle user authentication events with custom logic.

When you want to respond to HTTP requests with backend code without setting up a server.

When you want to process files uploaded to Firebase Storage automatically.

When you want to keep your app logic secure by running sensitive code on the backend.

Config File - firebase.json

firebase.json

{
  "functions": {
    "source": "functions"
  },
  "hosting": {
    "public": "public",
    "ignore": ["firebase.json", "**/.*", "**/node_modules/**"]
  }
}

This file tells Firebase where your serverless functions code lives under the functions folder. It also configures hosting settings for your app's static files.

Commands

This command sets up the serverless functions environment in your Firebase project, creating the necessary folders and files.

Terminal

firebase init functions

Expected Output

=== Functions Setup ===



You're about to initialize a Firebase Functions project.



✔  Wrote functions/package.json

✔  Wrote functions/index.js

✔  Wrote .eslintrc.js



Firebase initialization complete!

This command uploads and activates your serverless functions in Firebase, making them ready to respond to events or HTTP requests.

Terminal

firebase deploy --only functions

Expected Output

=== Deploying to 'your-project-id'...



i  deploying functions

Running command: npm --prefix "$RESOURCE_DIR" run lint



✔  functions: Finished running lint.



✔  functions: Finished running predeploy script.



✔  functions: functions folder uploaded successfully.



✔  Deploy complete!

→

--only functions - Deploy only the serverless functions without affecting other Firebase services.

This command opens a local shell to test your serverless functions without deploying them, so you can see how they behave.

Terminal

firebase functions:shell

Expected Output

✔  functions: Using node@16 from host.



⚠  functions: Emulator started.



firebase > 

Key Concept

Serverless functions let you add custom backend code to Firebase without managing servers, triggered by events or HTTP calls.

Common Mistakes

Trying to run serverless functions code without initializing the functions folder.

Firebase needs the functions folder and setup files to know where your backend code lives.

Always run 'firebase init functions' first to set up the environment.

Deploying the whole Firebase project when only functions changed.

This wastes time and can cause unintended changes to other services.

Use 'firebase deploy --only functions' to deploy just the functions.

Not testing functions locally before deploying.

You might deploy broken code that causes errors in production.

Use 'firebase functions:shell' to test functions locally first.

Summary

Initialize serverless functions in Firebase with 'firebase init functions'.

Deploy your functions using 'firebase deploy --only functions' to update backend code.

Test functions locally with 'firebase functions:shell' before deploying to catch errors early.

Practice

1. What is the main benefit of using serverless functions with Firebase?

easy

A. They only work on mobile devices.

B. You need to set up and maintain your own servers.

C. They replace the Firebase database completely.

D. You can run backend code without managing servers.

Solution

1. Step 1: Understand serverless functions

   Serverless functions let you write backend code that runs automatically without you managing servers.

2. Step 2: Compare options

   Serverless functions do not require server management, do not replace the database, and work on all platforms.

3. Final Answer:

   You can run backend code without managing servers. -> Option D

4. Quick Check:

   Serverless = no server management [OK]

Hint: Serverless means no servers to manage [OK]

Common Mistakes:

• Thinking serverless means no backend code
• Confusing serverless with database replacement
• Believing serverless only works on mobile

2. Which of the following is the correct way to define a Firebase serverless function triggered by a database write?

easy

A. exports.myFunc = functions.database.ref('/path').onWrite((change, context) => { /* code */ });

B. functions.database.onWrite('/path', (change, context) => { /* code */ });

C. exports.myFunc = functions.onWrite('/path', (change, context) => { /* code */ });

D. functions.database.ref('/path').write((change, context) => { /* code */ });

Solution

1. Step 1: Recall Firebase function syntax

   The correct syntax uses exports to define the function and functions.database.ref(path).onWrite() to trigger on database writes.

2. Step 2: Check each option

   exports.myFunc = functions.database.ref('/path').onWrite((change, context) => { /* code */ }); matches the correct syntax. The other options have incorrect method calls or missing exports.

3. Final Answer:

   exports.myFunc = functions.database.ref('/path').onWrite((change, context) => { /* code */ }); -> Option A

4. Quick Check:

   Correct Firebase function syntax = exports.myFunc = functions.database.ref('/path').onWrite((change, context) => { /* code */ }); [OK]

Hint: Look for exports and onWrite with ref path [OK]

Common Mistakes:

• Omitting exports keyword
• Using wrong method names like write instead of onWrite
• Incorrect function chaining order

3. Given this Firebase function code:

exports.greetUser = functions.auth.user().onCreate((user) => {
  return `Hello, ${user.email}!`;
});

What will this function do when a new user signs up?

medium

A. Return a greeting string but does not send it anywhere.

B. Trigger an error because return type is wrong.

C. Send a greeting email automatically.

D. Delete the user account immediately.

Solution

1. Step 1: Analyze function trigger and return

   The function triggers on user creation and returns a greeting string but does not send or log it anywhere.

2. Step 2: Understand side effects

   Returning a string alone does not send emails or cause errors. No deletion code is present.

3. Final Answer:

   Return a greeting string but does not send it anywhere. -> Option A

4. Quick Check:

   Return alone does not send email [OK]

Hint: Return value alone doesn't trigger actions [OK]

Common Mistakes:

• Assuming return sends email automatically
• Thinking function deletes user without code
• Believing return type causes error

4. You wrote this Firebase function:

exports.logChange = functions.database.ref('/items/{id}').onUpdate((change, context) => {
  console.log('Item updated');
});

But it never logs anything when the database updates. What is the likely problem?

medium

A. onUpdate is not a valid trigger method.

B. The database path '/items/{id}' is invalid syntax.

C. The function is missing a return statement or promise.

D. console.log cannot be used in Firebase functions.

Solution

1. Step 1: Check function structure

   Firebase functions should return a promise or value to signal completion. Missing return can cause silent failures.

2. Step 2: Validate other options

   Path syntax is correct, console.log works for debugging, and onUpdate is valid trigger.

3. Final Answer:

   The function is missing a return statement or promise. -> Option C

4. Quick Check:

   Return missing causes no execution [OK]

Hint: Always return or await in Firebase functions [OK]

Common Mistakes:

• Forgetting to return or await async work
• Assuming console.log doesn't work
• Misreading trigger method names

5. You want to extend your Firebase app to send a welcome email only when a new user signs up and their email is verified. Which approach best uses serverless functions to achieve this?

hard

A. Use a database trigger on user data write, ignoring email verification status.

B. Use an auth trigger on user creation, check if emailVerified is true, then send email.

C. Send emails directly from the client app after signup.

D. Use a scheduled function to send emails to all users daily.

Solution

1. Step 1: Identify correct trigger and condition

   Auth triggers on user creation allow checking user properties like emailVerified immediately.

2. Step 2: Evaluate options for sending email

   Use an auth trigger on user creation, check if emailVerified is true, then send email, which checks emailVerified before sending, ensuring only verified users get emails. The other options do not meet the requirement precisely.

3. Final Answer:

   Use an auth trigger on user creation, check if emailVerified is true, then send email. -> Option B

4. Quick Check:

   Auth trigger + emailVerified check = Use an auth trigger on user creation, check if emailVerified is true, then send email. [OK]

Hint: Check emailVerified in auth trigger before emailing [OK]

Common Mistakes:

• Sending emails without verifying email status
• Using database triggers for auth events
• Sending emails from client risking security