Functions with Cosmos DB integration in Azure - Time & Space Complexity

Time Complexity: Functions with Cosmos DB integration

O(n)

Understanding Time Complexity

When using Azure Functions with Cosmos DB, it is important to understand how the number of database operations affects the overall execution time.

We want to know how the time to complete the function grows as the amount of data or requests increases.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

// Azure Function triggered by HTTP request
public static async Task<IActionResult> Run(HttpRequest req, ILogger log)
{
    var client = new CosmosClient("connection-string");
    var container = client.GetContainer("database", "container");
    string query = "SELECT * FROM c WHERE c.type = 'item'";
    var iterator = container.GetItemQueryIterator<Item>(query);
    List<Item> results = new List<Item>();
    while (iterator.HasMoreResults)
    {
        var response = await iterator.ReadNextAsync();
        results.AddRange(response.Resource);
    }
    return new OkObjectResult(results);
}

This function queries Cosmos DB for all items of a certain type and returns them in the response.

Identify Repeating Operations

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

• Primary operation: Calls to ReadNextAsync() to fetch pages of query results from Cosmos DB.
• How many times: Once per page of results until all items are retrieved.

How Execution Grows With Input

Each page fetch retrieves a fixed number of items. As the total number of items grows, the number of page fetches grows roughly in proportion.

Input Size (n)	Approx. Api Calls/Operations
10	1
100	~10
1000	~100

Pattern observation: The number of API calls grows linearly with the number of items retrieved.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete the function grows directly in proportion to the number of items returned from Cosmos DB.

Common Mistake

[X] Wrong: "Fetching all items from Cosmos DB happens in a single call regardless of data size."

[OK] Correct: Cosmos DB returns results in pages, so multiple calls are needed as data grows, increasing total time.

Interview Connect

Understanding how cloud functions interact with databases and how data size affects performance is a key skill for building scalable applications.

Self-Check

What if the function filtered items inside the code instead of in the query? How would the time complexity change?

Practice

1. What is the main benefit of using Azure Functions with Cosmos DB integration?

easy

A. Automatically run code when data changes in Cosmos DB

B. Manually trigger code only through HTTP requests

C. Store large files directly in Cosmos DB

D. Replace Cosmos DB with Azure Blob Storage

Solution

1. Step 1: Understand Azure Functions with Cosmos DB

   Azure Functions can be triggered automatically by changes in Cosmos DB data.

2. Step 2: Identify the main benefit

   This automatic trigger saves resources by running code only when needed, without manual calls.

3. Final Answer:

   Automatically run code when data changes in Cosmos DB -> Option A

4. Quick Check:

   Functions trigger on data changes = A [OK]

Hint: Functions run on data change events automatically [OK]

Common Mistakes:

• Thinking functions run only on HTTP triggers
• Confusing Cosmos DB with file storage
• Assuming manual triggers are required

2. Which of the following is the correct binding direction for a Cosmos DB input binding in an Azure Function?

easy

A. direction: "out"

B. direction: "both"

C. direction: "trigger"

D. direction: "in"

Solution

1. Step 1: Recall binding directions

   Input bindings receive data into the function, so their direction is "in".

2. Step 2: Match binding direction for Cosmos DB input

   Cosmos DB input binding must have direction set to "in" to read data.

3. Final Answer:

   direction: "in" -> Option D

4. Quick Check:

   Input binding direction = in [OK]

Hint: Input bindings always use direction "in" [OK]

Common Mistakes:

• Using "out" for input bindings
• Confusing trigger with input binding
• Using invalid directions like "both"

3. Given this Azure Function code snippet triggered by Cosmos DB changes, what will be logged if a new document with id "123" is added?

module.exports = async function (context, documents) {
  if (!!documents && documents.length > 0) {
    context.log(`Document id: ${documents[0].id}`);
  }
};

medium

A. No output logged

B. Document id: undefined

C. Document id: 123

D. Error: documents is not defined

Solution

1. Step 1: Understand the trigger input

   The function receives an array 'documents' with changed documents; the first document has id "123".

2. Step 2: Analyze the logging statement

   The code logs the id of the first document, which is "123".

3. Final Answer:

   Document id: 123 -> Option C

4. Quick Check:

   documents[0].id = 123 logged [OK]

Hint: documents array holds changed items; access first with documents[0] [OK]

Common Mistakes:

• Assuming documents is undefined
• Logging without checking documents length
• Confusing document id property

4. You wrote an Azure Function triggered by Cosmos DB changes, but it never runs when documents change. Which is the most likely cause?

medium

A. The function code has a syntax error

B. The function.json binding has incorrect connection string name

C. The Cosmos DB container is empty

D. The function app is stopped

Solution

1. Step 1: Check trigger configuration

   If the connection string name in function.json is wrong, the function won't connect to Cosmos DB changes.

2. Step 2: Consider other causes

   Syntax errors cause failures but usually show errors; empty container still triggers on inserts; stopped app won't run but question implies function exists.

3. Final Answer:

   The function.json binding has incorrect connection string name -> Option B

4. Quick Check:

   Wrong connection string stops trigger [OK]

Hint: Check connection string name in function.json first [OK]

Common Mistakes:

• Ignoring binding configuration errors
• Assuming empty container prevents triggers
• Not verifying function app status

5. You want to create an Azure Function that writes a summary document to Cosmos DB whenever multiple documents are added. Which binding setup should you use?

hard

A. Use Cosmos DB trigger for input and Cosmos DB output binding for summary document

B. Use HTTP trigger and Cosmos DB input binding only

C. Use Cosmos DB input binding only, no trigger

D. Use Timer trigger and Cosmos DB output binding only

Solution

1. Step 1: Identify trigger for reacting to data changes

   Cosmos DB trigger runs the function automatically when documents change.

2. Step 2: Use output binding to write summary

   Output binding lets the function write a new summary document back to Cosmos DB.

3. Final Answer:

   Use Cosmos DB trigger for input and Cosmos DB output binding for summary document -> Option A

4. Quick Check:

   Trigger input + output binding for writing = C [OK]

Hint: Trigger on changes, output binding to write summary [OK]

Common Mistakes:

• Using HTTP trigger instead of Cosmos DB trigger
• Missing output binding for writing data
• Using timer trigger without data event