Hosting setup and deployment in Firebase - Time & Space Complexity

Time Complexity: Hosting setup and deployment

O(n)

Understanding Time Complexity

When setting up and deploying hosting on Firebase, it's important to know how the time to complete these steps changes as your project grows.

We want to understand how the deployment process scales with the size of your website or app files.

Scenario Under Consideration

Analyze the time complexity of deploying a website using Firebase Hosting CLI.

firebase login
firebase init hosting
firebase deploy --only hosting
    

This sequence logs in, initializes hosting setup, and deploys the website files to Firebase Hosting.

Identify Repeating Operations

Look at what happens multiple times during deployment.

• Primary operation: Uploading each file from your project to Firebase servers.
• How many times: Once per file in your website or app folder.

How Execution Grows With Input

As you add more files, the deployment takes longer because each file is sent separately.

Input Size (n)	Approx. Api Calls/Operations
10 files	About 10 upload operations
100 files	About 100 upload operations
1000 files	About 1000 upload operations

Pattern observation: The number of upload operations grows directly with the number of files.

Final Time Complexity

Time Complexity: O(n)

This means the deployment time grows in a straight line with the number of files you have to upload.

Common Mistake

[X] Wrong: "Deploying takes the same time no matter how many files I have."

[OK] Correct: Each file must be uploaded separately, so more files mean more upload steps and longer deployment.

Interview Connect

Understanding how deployment time grows helps you plan and explain your cloud workflows clearly, a useful skill in real projects and discussions.

Self-Check

What if Firebase used batch uploading to send multiple files at once? How would the time complexity change?

Practice

1. What is the main purpose of Firebase Hosting?

easy

A. To create databases for mobile apps

B. To write backend server code

C. To publish websites online without managing servers

D. To monitor app performance

Solution

1. Step 1: Understand Firebase Hosting's role

   Firebase Hosting is designed to host and serve web content easily without needing to manage servers.

2. Step 2: Differentiate from other Firebase services

   Other services like databases or backend code are separate from Hosting's purpose.

3. Final Answer:

   To publish websites online without managing servers -> Option C

4. Quick Check:

   Firebase Hosting = publish websites without servers [OK]

Hint: Remember Hosting is for websites, not databases or code [OK]

Common Mistakes:

• Confusing Hosting with Firebase database services
• Thinking Hosting manages backend code
• Assuming Hosting monitors app performance

2. Which command initializes Firebase Hosting in your project?

easy

A. firebase init hosting

B. firebase deploy --only hosting

C. firebase start hosting

D. firebase create hosting

Solution

1. Step 1: Identify the initialization command

   The command to set up Firebase Hosting configuration is firebase init hosting.

2. Step 2: Differentiate from deployment commands

   firebase deploy --only hosting publishes the site but does not initialize it.

3. Final Answer:

   firebase init hosting -> Option A

4. Quick Check:

   Initialize Hosting = firebase init hosting [OK]

Hint: Init sets up Hosting; deploy publishes it [OK]

Common Mistakes:

• Using deploy command to initialize
• Assuming 'firebase start hosting' exists
• Confusing create with init

3. After running firebase deploy --only hosting, what happens?

medium

A. Firebase deletes your local project files

B. Your website files are uploaded and become live at a Firebase URL

C. Your database is reset to default

D. Firebase Hosting configuration is removed

Solution

1. Step 1: Understand the deploy command effect

   The deploy command uploads your site files to Firebase Hosting and makes the site live.

2. Step 2: Eliminate incorrect options

   Deploy does not delete local files, reset databases, or remove configuration.

3. Final Answer:

   Your website files are uploaded and become live at a Firebase URL -> Option B

4. Quick Check:

   Deploy Hosting = upload and go live [OK]

Hint: Deploy publishes your site live on Firebase URL [OK]

Common Mistakes:

• Thinking deploy deletes local files
• Confusing deploy with database reset
• Assuming deploy removes Hosting setup

4. You ran firebase deploy --only hosting but your site did not update. What is a likely cause?

medium

A. You deployed to the wrong Firebase project

B. Your internet connection was too fast

C. You forgot to run firebase init hosting first

D. Firebase Hosting does not support updates

Solution

1. Step 1: Check project targeting

   If you deploy to the wrong Firebase project, your site won't update as expected.

2. Step 2: Rule out other options

   Init is needed only once; internet speed does not block updates; Hosting supports updates.

3. Final Answer:

   You deployed to the wrong Firebase project -> Option A

4. Quick Check:

   Wrong project deploy = no site update [OK]

Hint: Verify project ID before deploying [OK]

Common Mistakes:

• Assuming init must run every deploy
• Blaming internet speed for deployment failure
• Thinking Hosting can't update sites

5. You want to deploy only your website without affecting other Firebase services. Which command should you use?

hard

A. firebase deploy

B. firebase deploy --only database

C. firebase deploy --except hosting

D. firebase deploy --only hosting

Solution

1. Step 1: Understand deployment scope flags

   The --only hosting flag deploys just the Hosting service, leaving others untouched.

2. Step 2: Compare other options

   firebase deploy deploys all configured services; --only database deploys only database; --except hosting deploys all except Hosting.

3. Final Answer:

   firebase deploy --only hosting -> Option D

4. Quick Check:

   Deploy only Hosting = firebase deploy --only hosting [OK]

Hint: Use --only hosting to deploy just the website [OK]

Common Mistakes:

• Running deploy without --only and affecting all services
• Using --only database instead of hosting
• Using --except hosting to deploy Hosting