Why serverless functions extend Firebase - See It in Action

Why Serverless Functions Extend Firebase

📖 Scenario: You are building a simple app using Firebase. You want to add custom backend logic without managing servers.

🎯 Goal: Learn how to create and deploy a serverless function in Firebase to extend app capabilities.

📋 What You'll Learn

Create a Firebase Cloud Function that responds to HTTP requests

Add a configuration variable to customize the function behavior

Implement the core logic to handle the request and send a response

Deploy the function with proper export to Firebase

💡 Why This Matters

🌍 Real World

Serverless functions let you add backend features to your Firebase app without managing servers. This is useful for sending emails, processing data, or customizing responses.

💼 Career

Understanding serverless functions is important for cloud developers and backend engineers working with Firebase or other cloud platforms.

1

Set up a basic Firebase Cloud Function

Create a Firebase Cloud Function named helloWorld that responds to HTTP requests and sends back the text 'Hello from Firebase!'. Use functions.https.onRequest and the parameters request and response.

Firebase

const functions = require('firebase-functions');

// Your code here

Hint

Use exports.helloWorld = functions.https.onRequest((request, response) => { ... }) to create the function.

2

Add a configuration variable for greeting

Add a variable named greeting and set it to the string 'Hello from Firebase Functions!'. Use this variable inside the helloWorld function to send the response instead of the fixed string.

Firebase

const functions = require('firebase-functions');

// Your code here

exports.helloWorld = functions.https.onRequest((request, response) => {
  response.send(greeting);
});

Hint

Define const greeting = 'Hello from Firebase Functions!' before the function and use it in response.send(greeting).

3

Implement core logic to customize greeting with query parameter

Inside the helloWorld function, check if the HTTP request has a query parameter named name. If it exists, send back 'Hello, <name>!' where <name> is the parameter value. Otherwise, send the default greeting.

Firebase

const functions = require('firebase-functions');

const greeting = 'Hello from Firebase Functions!';

exports.helloWorld = functions.https.onRequest((request, response) => {
  // Your code here
});

Hint

Use const name = request.query.name and an if statement to check it.

4

Export and deploy the function properly

Ensure the helloWorld function is exported using exports.helloWorld so Firebase can deploy it. The full code should be ready for deployment.

Firebase

const functions = require('firebase-functions');

const greeting = 'Hello from Firebase Functions!';

// Your code here to export the function

Hint

Make sure the function is exported with exports.helloWorld = ....

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