Modules for reusability in GCP - Time & Space Complexity

Time Complexity: Modules for reusability

O(n)

Understanding Time Complexity

When using modules in cloud infrastructure, it is important to understand how the time to deploy or update resources changes as we reuse modules multiple times.

We want to know how the number of module calls affects the total operations performed.

Scenario Under Consideration

Analyze the time complexity of deploying multiple instances of a module.

module "storage_bucket" {
  source = "./modules/bucket"
  count  = var.bucket_count
  name   = "bucket-${count.index}"
}

variable "bucket_count" {
  type    = number
  default = 3
}

This code deploys a number of storage buckets by calling the same module multiple times with different names.

Identify Repeating Operations

Identify the API calls and resource provisioning that repeat.

• Primary operation: Creating a storage bucket resource via the module.
• How many times: Equal to the number of module instances (var.bucket_count).

How Execution Grows With Input

Each additional module instance adds one more resource creation operation.

Input Size (n)	Approx. API Calls/Operations
10	10 bucket creation calls
100	100 bucket creation calls
1000	1000 bucket creation calls

Pattern observation: The number of operations grows directly with the number of module instances.

Final Time Complexity

Time Complexity: O(n)

This means the time to deploy grows linearly as you add more module instances.

Common Mistake

[X] Wrong: "Using modules means deployment time stays the same no matter how many instances."

[OK] Correct: Each module instance creates its own resources, so more instances mean more work and longer deployment time.

Interview Connect

Understanding how module reuse affects deployment time shows you grasp how cloud resources scale and how to plan infrastructure efficiently.

Self-Check

"What if the module itself creates multiple resources internally? How would that affect the overall time complexity?"

Practice

1. What is the main benefit of using modules in GCP infrastructure setup?

easy

A. They let you reuse code to create cloud resources easily.

B. They automatically fix errors in your cloud setup.

C. They increase the cost of cloud resources.

D. They replace the need for any configuration files.

Solution

1. Step 1: Understand what modules do

   Modules are reusable pieces of configuration that help you avoid repeating code.

2. Step 2: Identify the benefit in context

   Using modules makes your cloud setup easier and faster by reusing code.

3. Final Answer:

   They let you reuse code to create cloud resources easily. -> Option A

4. Quick Check:

   Modules = Reuse code [OK]

Hint: Modules help reuse code to save time and effort [OK]

Common Mistakes:

• Thinking modules fix errors automatically
• Believing modules increase costs
• Assuming modules remove all config files

2. Which of the following is the correct way to call a module in a Terraform configuration for GCP?

easy

A. module "storage" { source = "./modules/storage" }

B. call module storage from "./modules/storage"

C. use module storage located at ./modules/storage

D. import module storage from "./modules/storage"

Solution

1. Step 1: Recall Terraform module syntax

   Terraform uses the keyword module followed by a name and a block with source to specify the module path.

2. Step 2: Match the correct syntax

   module "storage" { source = "./modules/storage" } matches the correct syntax: module "name" { source = "path" }.

3. Final Answer:

   module "storage" { source = "./modules/storage" } -> Option A

4. Quick Check:

   Terraform module call = module "name" with source [OK]

Hint: Use 'module "name" { source = "path" }' to call modules [OK]

Common Mistakes:

• Using keywords like call or import which are invalid
• Missing quotes around module name
• Not using a block structure for module

3. Given this Terraform module call:

module "network" {
  source = "./modules/network"
  region = "us-central1"
}

What will happen if the module network does not accept a region variable?

medium

A. Terraform will deploy but with a default region.

B. Terraform will ignore the extra variable and deploy successfully.

C. Terraform will throw an error about an unknown variable.

D. Terraform will deploy but skip the network module.

Solution

1. Step 1: Understand variable passing in modules

   Terraform requires that variables passed to modules must be declared in the module's variables file.

2. Step 2: Identify behavior when unknown variable is passed

   If a variable is passed but not declared, Terraform throws an error about unknown input variable.

3. Final Answer:

   Terraform will throw an error about an unknown variable. -> Option C

4. Quick Check:

   Unknown module variable = error [OK]

Hint: Modules must declare variables before use [OK]

Common Mistakes:

• Assuming Terraform ignores unknown variables
• Thinking Terraform uses defaults without declaration
• Believing module is skipped silently

4. You have a module defined in ./modules/storage but when you run Terraform apply, it fails with:
Error: Module not found
What is the most likely cause?

medium

A. Terraform does not support modules in local folders.

B. The module code has syntax errors inside it.

C. You forgot to initialize the Terraform backend.

D. The source path in the module call is incorrect or misspelled.

Solution

1. Step 1: Understand the error meaning

   The error 'Module not found' means Terraform cannot locate the module source path.

2. Step 2: Check common causes

   The most common cause is a wrong or misspelled source path in the module call.

3. Final Answer:

   The source path in the module call is incorrect or misspelled. -> Option D

4. Quick Check:

   Module not found = wrong source path [OK]

Hint: Check module source path spelling if module not found error [OK]

Common Mistakes:

• Assuming syntax errors cause 'Module not found'
• Thinking Terraform disallows local modules
• Confusing backend init with module loading

5. You want to create multiple GCP VM instances with similar settings using a module. Which approach best uses modules for reusability and scalability?

hard

A. Use a module only once and duplicate its code for other VMs.

B. Create a module for one VM and call it multiple times with different instance names.

C. Create separate modules for each VM with hardcoded settings.

D. Write all VM configurations directly in the main file without modules.

Solution

1. Step 1: Understand module reusability

   Modules let you reuse the same configuration by calling them multiple times with different inputs.

2. Step 2: Identify scalable approach

   Calling one VM module multiple times with different names is scalable and clean.

3. Final Answer:

   Create a module for one VM and call it multiple times with different instance names. -> Option B

4. Quick Check:

   Reuse module calls for multiple resources [OK]

Hint: Call one module multiple times with different inputs [OK]

Common Mistakes:

• Duplicating module code instead of reusing
• Hardcoding settings in separate modules
• Avoiding modules and repeating code