Functions with Cosmos DB integration in Azure - Step-by-Step Execution

Process Flow - Functions with Cosmos DB integration

Trigger: HTTP Request or Timer

↓

Azure Function Starts

↓

Read/Write to Cosmos DB

↓

Process Data

↓

Return Response or Complete

↓

Function Ends

The function starts on a trigger, interacts with Cosmos DB to read or write data, processes it, then returns a response or completes.

Execution Sample

Azure

module.exports = async function (context, req) {
  const item = req.body;
  context.bindings.outputDocument = item;
  context.res = { status: 201, body: 'Item saved' };
};

This Azure Function receives data from an HTTP request and saves it to Cosmos DB using output binding.

Process Table

Step	Action	Input/State	Cosmos DB Interaction	Output/Result
1	Function triggered by HTTP request	Request body with item data	No interaction yet	Function starts
2	Read request body	{ id: '123', name: 'Test' }	No interaction	Item extracted from request
3	Assign item to Cosmos DB output binding	Item data assigned	Prepare to write item to Cosmos DB	Binding set for write
4	Await Cosmos DB write operation	Waiting for DB confirmation	Write item to Cosmos DB collection	Item saved in DB
5	Set HTTP response	Status 201, message 'Item saved'	No interaction	Response ready to send
6	Function completes	Response sent	No interaction	Function ends

💡 Function ends after sending HTTP response confirming Cosmos DB write

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
context	Initialized	Request body read	Output binding set	Awaiting DB write	Response set
item	Undefined	{ id: '123', name: 'Test' }	{ id: '123', name: 'Test' }	{ id: '123', name: 'Test' }	{ id: '123', name: 'Test' }
context.res	Undefined	Undefined	Undefined	Undefined	{ status: 201, body: 'Item saved' }

Key Moments - 3 Insights

Why do we assign the item to context.bindings.outputDocument instead of calling Cosmos DB directly?

Azure Functions use bindings to simplify integration. Assigning to outputDocument tells the platform to write to Cosmos DB automatically, as shown in step 3 and 4 of the execution_table.

What happens if the Cosmos DB write fails during the await operation?

The function will throw an error during step 4, stopping execution before setting the response. Proper error handling is needed to manage this, which is not shown here.

Why is the HTTP response set after awaiting the Cosmos DB write?

We wait for confirmation that the data is saved before responding, ensuring the client knows the operation succeeded, as seen in step 5.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of 'item' after step 2?

A Empty object {}

B { id: '123', name: 'Test' }

C Undefined

D Null

💡 Hint

Check the 'Input/State' column at step 2 in execution_table

At which step does the function write data to Cosmos DB?

A Step 4

B Step 2

C Step 3

D Step 5

💡 Hint

Look at the 'Cosmos DB Interaction' column to find when the write happens

If the HTTP response was set before awaiting Cosmos DB write, what would change in the execution_table?

A Step 6 would be earlier

B Step 4 would be removed

C Step 5 would occur before step 4

D No change

💡 Hint

Consider the order of 'Set HTTP response' and 'Await Cosmos DB write operation' steps

Concept Snapshot

Azure Functions with Cosmos DB integration use bindings to connect easily.
Trigger starts function, input data is read.
Assign data to output binding to save in Cosmos DB.
Await completion before sending response.
This ensures data is saved before client is notified.

Full Transcript

This visual execution shows how an Azure Function integrates with Cosmos DB using output bindings. The function triggers on an HTTP request, reads the request body, assigns the data to the Cosmos DB output binding, waits for the database write to complete, then sends an HTTP response confirming the save. Variables like 'item' and 'context.res' change state step-by-step. Key moments clarify why bindings are used and why awaiting the database write is important. The quiz tests understanding of the execution order and variable states.