Firebase Admin SDK (Node.js) - Time & Space Complexity

Time Complexity: Firebase Admin SDK (Node.js)

O(n)

Understanding Time Complexity

When using the Firebase Admin SDK in Node.js, it's important to understand how the number of operations grows as you interact with your database or services.

We want to know how the time it takes changes when we handle more data or requests.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

const admin = require('firebase-admin');
admin.initializeApp();

const db = admin.firestore();

async function getUsersData(userIds) {
  const usersData = [];
  for (const id of userIds) {
    const doc = await db.collection('users').doc(id).get();
    usersData.push(doc.data());
  }
  return usersData;
}

This code fetches user data from Firestore for each user ID in a list, one by one.

Identify Repeating Operations

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

• Primary operation: Firestore document read via doc(id).get() call.
• How many times: Once for each user ID in the input list.

How Execution Grows With Input

Each user ID causes one separate read request to Firestore, so the total number of reads grows directly with the number of user IDs.

Input Size (n)	Approx. API Calls/Operations
10	10 document reads
100	100 document reads
1000	1000 document reads

Pattern observation: The number of API calls increases linearly as the input size increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete grows directly in proportion to the number of user IDs you fetch.

Common Mistake

[X] Wrong: "Fetching multiple documents one by one is as fast as fetching them all at once."

[OK] Correct: Each separate fetch makes its own network call, so doing many one-by-one calls takes longer than batching or parallel fetching.

Interview Connect

Understanding how your code scales with more data is a key skill. It shows you can write efficient cloud code that handles growth smoothly.

Self-Check

"What if we changed the code to fetch all user documents in a single batch call? How would the time complexity change?"

Practice

1. What is the primary purpose of the Firebase Admin SDK in Node.js?

easy

A. To build user interfaces for Firebase apps

B. To securely manage Firebase services from a server environment

C. To run Firebase apps directly in the browser

D. To replace Firebase client SDK on mobile devices

Solution

1. Step 1: Understand Firebase Admin SDK role

   The Admin SDK is designed for server-side use to manage Firebase services securely.

2. Step 2: Differentiate from client SDKs

   Client SDKs run on user devices for app interaction, while Admin SDK runs on servers for management tasks.

3. Final Answer:

   To securely manage Firebase services from a server environment -> Option B

4. Quick Check:

   Admin SDK = server management [OK]

Hint: Admin SDK is for backend server tasks, not frontend apps [OK]

Common Mistakes:

• Confusing Admin SDK with client SDK
• Thinking Admin SDK runs in browsers
• Assuming Admin SDK builds UI

2. Which of the following is the correct way to initialize the Firebase Admin SDK in Node.js using a service account JSON file named serviceAccountKey.json?

easy

A. const admin = require('firebase-admin');
admin.initializeApp({credential: admin.credential.cert(require('./serviceAccountKey.json'))});

B. const admin = require('firebase-admin');
admin.initializeApp({serviceAccount: 'serviceAccountKey.json'});

C. const admin = require('firebase-admin');
admin.initializeApp({credential: admin.credential.applicationDefault()});

D. const admin = require('firebase-admin');
admin.initializeApp({credential: admin.credential.cert(serviceAccountKey.json)});

Solution

1. Step 1: Load service account JSON correctly

   The service account JSON must be imported using require to pass the object, not a string path.

2. Step 2: Use admin.credential.cert with the JSON object

   Pass the imported JSON object to admin.credential.cert for proper initialization.

3. Final Answer:

   const admin = require('firebase-admin'); admin.initializeApp({credential: admin.credential.cert(require('./serviceAccountKey.json'))}); -> Option A

4. Quick Check:

   Use require() to load JSON for cert [OK]

Hint: Use require() to load JSON, not a string path [OK]

Common Mistakes:

• Passing file path string instead of JSON object
• Using applicationDefault() when service account is needed
• Incorrect property name like 'serviceAccount'

3. Given the following Node.js code using Firebase Admin SDK, what will be the output if the user with UID 'user123' exists?

const admin = require('firebase-admin');
admin.initializeApp();

admin.auth().getUser('user123')
  .then(userRecord => console.log(userRecord.uid))
  .catch(error => console.log('Error:', error.message));

medium

A. user123

B. Error: User not found

C. undefined

D. null

Solution

1. Step 1: Understand getUser() behavior

   getUser() returns a Promise resolving to a user record if the user exists.

2. Step 2: Check the then() callback output

   The code logs userRecord.uid, which will be 'user123' if the user exists.

3. Final Answer:

   user123 -> Option A

4. Quick Check:

   getUser() returns user data, logs UID [OK]

Hint: getUser() returns user info; log uid to see user ID [OK]

Common Mistakes:

• Assuming getUser() returns error if user exists
• Expecting undefined or null instead of UID
• Not handling Promise correctly

4. Identify the error in the following Firebase Admin SDK Node.js code snippet:

const admin = require('firebase-admin');
admin.initializeApp({
  credential: admin.credential.cert(serviceAccountKey.json)
});

admin.auth().createUser({
  email: '[e-mail]',
  password: 'secret123'
}).then(userRecord => console.log(userRecord.uid));

medium

A. initializeApp() cannot accept credential property

B. Password must be at least 10 characters

C. createUser() requires a displayName field

D. The service account JSON file path should be required, not passed as a string

Solution

1. Step 1: Check initialization of credential

   admin.credential.cert() expects a JSON object, not a string path. The file must be loaded with require().

2. Step 2: Validate other parameters

   Password length and displayName are optional or valid; initializeApp() accepts credential property.

3. Final Answer:

   The service account JSON file path should be required, not passed as a string -> Option D

4. Quick Check:

   Use require() to load JSON for cert [OK]

Hint: Load JSON with require(), not string path [OK]

Common Mistakes:

• Passing string path instead of JSON object
• Assuming password length error
• Thinking displayName is mandatory

5. You want to send a push notification to a device using Firebase Admin SDK in Node.js. Which sequence of steps correctly applies to achieve this?

hard

A. Use Firebase client SDK to send notification directly from server without Admin SDK

B. Initialize Admin SDK with credentials, call admin.auth().sendNotification(token, message), then handle response

C. Initialize Admin SDK with credentials, build a message object with token and notification, then call admin.messaging().send(message)

D. Initialize Admin SDK without credentials, build message, then call admin.database().send(message)

Solution

1. Step 1: Initialize Admin SDK properly

   Admin SDK must be initialized with credentials to access Firebase services securely.

2. Step 2: Create message object and send

   Build a message with device token and notification details, then use admin.messaging().send() to send it.

3. Final Answer:

   Initialize Admin SDK with credentials, build a message object with token and notification, then call admin.messaging().send(message) -> Option C

4. Quick Check:

   Use admin.messaging().send() with message object [OK]

Hint: Use admin.messaging().send() with message object and token [OK]

Common Mistakes:

• Using auth() instead of messaging() for notifications
• Trying to send without initializing SDK
• Using database() to send notifications