Pub/Sub with Cloud Functions integration in GCP - Time & Space Complexity

Time Complexity: Pub/Sub with Cloud Functions integration

O(n)

Understanding Time Complexity

When using Pub/Sub with Cloud Functions, it's important to understand how the number of messages affects processing time.

We want to know how the system scales as more messages arrive.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

// Create a Pub/Sub topic
const topic = pubsub.topic('my-topic');

// Deploy a Cloud Function triggered by the topic
exports.processMessage = (message, context) => {
  const data = Buffer.from(message.data, 'base64').toString();
  // Process the message data
  console.log(`Received message: ${data}`);
};

This sequence sets up a Pub/Sub topic and a Cloud Function that runs each time a message is published to the topic.

Identify Repeating Operations

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

• Primary operation: Cloud Function invocation triggered by each Pub/Sub message.
• How many times: Once per message published to the topic.

How Execution Grows With Input

Each new message causes one Cloud Function run, so the total work grows directly with the number of messages.

Input Size (n)	Approx. Api Calls/Operations
10	10 function invocations
100	100 function invocations
1000	1000 function invocations

Pattern observation: The number of function calls grows linearly as messages increase.

Final Time Complexity

Time Complexity: O(n)

This means the total processing time grows in direct proportion to the number of messages.

Common Mistake

[X] Wrong: "The Cloud Function runs only once no matter how many messages arrive."

[OK] Correct: Each message triggers a separate function run, so more messages mean more executions.

Interview Connect

Understanding how event-driven systems scale helps you design efficient cloud solutions and answer real-world questions confidently.

Self-Check

"What if the Cloud Function batches multiple messages in one invocation? How would the time complexity change?"

Practice

1.

What is the main role of Google Cloud Pub/Sub when integrated with Cloud Functions?

easy

A. To send messages that trigger Cloud Functions automatically

B. To store large files for Cloud Functions to process

C. To provide a user interface for Cloud Functions

D. To manage user authentication for Cloud Functions

Solution

1. Step 1: Understand Pub/Sub's purpose

   Pub/Sub is designed to send messages between parts of an app, acting as a messenger.

2. Step 2: Connect Pub/Sub with Cloud Functions

   Cloud Functions run code automatically when they receive messages from Pub/Sub.

3. Final Answer:

   To send messages that trigger Cloud Functions automatically -> Option A

4. Quick Check:

   Pub/Sub triggers Cloud Functions [OK]

Hint: Pub/Sub sends messages; Cloud Functions react to them [OK]

Common Mistakes:

• Thinking Pub/Sub stores files
• Confusing Pub/Sub with UI or authentication
• Assuming Cloud Functions manage user login

2.

Which of the following is the correct way to specify a Pub/Sub trigger in a Cloud Function deployment command?

gcloud functions deploy myFunction --trigger-?

easy

A. --trigger-http my-topic

B. --trigger-bucket my-topic

C. --trigger-topic my-topic

D. --trigger-event my-topic

Solution

1. Step 1: Identify the trigger type for Pub/Sub

   Pub/Sub triggers require specifying the topic name with --trigger-topic.

2. Step 2: Match the correct flag

   --trigger-topic is the correct flag; others relate to storage or HTTP triggers.

3. Final Answer:

   --trigger-topic my-topic -> Option C

4. Quick Check:

   Pub/Sub trigger uses --trigger-topic [OK]

Hint: Pub/Sub triggers use --trigger-topic flag [OK]

Common Mistakes:

• Using --trigger-bucket which is for Cloud Storage
• Using --trigger-http which is for HTTP triggers
• Confusing event triggers with topic triggers

3.

Given this Cloud Function code triggered by Pub/Sub messages, what will be logged when a message with data "Hello" is published?

def hello_pubsub(event, context):
    import base64
    message = base64.b64decode(event['data']).decode('utf-8')
    print(f"Received message: {message}")

medium

A. Received message: event['data']

B. Received message: Hello

C. Received message: b'Hello'

D. Error: 'data' key missing

Solution

1. Step 1: Decode the Pub/Sub message data

   The message data is base64 encoded; decoding it gives the original string "Hello".

2. Step 2: Print the decoded message

   The print statement outputs "Received message: Hello" exactly.

3. Final Answer:

   Received message: Hello -> Option B

4. Quick Check:

   Base64 decode then print = Received message: Hello [OK]

Hint: Decode base64 data to get original message [OK]

Common Mistakes:

• Printing raw base64 bytes instead of decoded string
• Using event['data'] directly without decoding
• Assuming 'data' key is missing

4.

What is the likely cause if a Cloud Function triggered by Pub/Sub never runs after publishing messages?

medium

A. The Cloud Function is not subscribed to the correct Pub/Sub topic

B. The Cloud Function code has a syntax error

C. The Pub/Sub topic does not exist

D. The Cloud Function has too much memory allocated

Solution

1. Step 1: Check the Cloud Function trigger configuration

   If the function is not subscribed to the right topic, it won't receive messages.

2. Step 2: Rule out other causes

   Syntax errors cause deployment failure, not silent no-run; topic existence is needed but usually checked; memory size doesn't stop triggers.

3. Final Answer:

   The Cloud Function is not subscribed to the correct Pub/Sub topic -> Option A

4. Quick Check:

   Wrong topic subscription = no trigger [OK]

Hint: Check topic subscription if function never runs [OK]

Common Mistakes:

• Assuming syntax error causes silent no-run
• Ignoring topic existence or permissions
• Blaming memory size for trigger issues

5.

You want to build a system where multiple Cloud Functions react independently to the same Pub/Sub messages. What is the best way to set this up?

hard

A. Publish messages multiple times to different topics

B. Create multiple Pub/Sub topics, each with one Cloud Function subscription

C. Use one Cloud Function that calls other functions internally

D. Create one Pub/Sub topic and multiple subscriptions, each triggering a different Cloud Function

Solution

1. Step 1: Understand Pub/Sub fan-out pattern

   One topic can have multiple subscriptions; each subscription can trigger a different Cloud Function independently.

2. Step 2: Compare options

   Multiple topics add complexity; one function calling others is indirect; publishing multiple times is inefficient.

3. Final Answer:

   Create one Pub/Sub topic and multiple subscriptions, each triggering a different Cloud Function -> Option D

4. Quick Check:

   One topic, many subscriptions = multiple triggers [OK]

Hint: Use multiple subscriptions on one topic for parallel triggers [OK]

Common Mistakes:

• Creating many topics unnecessarily
• Using one function to call others instead of triggers
• Publishing duplicate messages to multiple topics