You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cosmos-db/change-feed-functions.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,21 +11,21 @@ ms.reviewer: sngun
11
11
12
12
# Serverless event-based architectures with Azure Cosmos DB and Azure Functions
13
13
14
-
Azure Functions provides the simplest way to connect to the Change Feed. You can create small reactive Azure Functions that will be automatically triggered on each new event in your Azure Cosmos container's Change Feed.
14
+
Azure Functions provides the simplest way to connect to the [change feed](). You can create small reactive Azure Functions that will be automatically triggered on each new event in your Azure Cosmos container's change feed.
15
15
16
16

17
17
18
-
With the [Azure Cosmos DB Trigger](../azure-functions/functions-bindings-cosmosdb-v2.md#trigger), you can leverage the [Change Feed Processor](./change-feed-processor.md) scalability and reliable event detection without the need to maintain any [worker infrastructure](./change-feed-processor.md#implementing-the-change-feed-processor-library). Just focus on your Azure Function's logic without worrying about the rest of the event-sourcing pipeline. You can even mix the Trigger with any other [Azure Functions bindings](../azure-functions/functions-triggers-bindings.md#supported-bindings).
18
+
With the [Azure Cosmos DB Trigger](../azure-functions/functions-bindings-cosmosdb-v2.md#trigger), you can leverage the [Change Feed Processor](./change-feed-processor.md)'s scaling and reliable event detection functionality without the need to maintain any [worker infrastructure](./change-feed-processor.md#implementing-the-change-feed-processor-library). Just focus on your Azure Function's logic without worrying about the rest of the event-sourcing pipeline. You can even mix the Trigger with any other [Azure Functions bindings](../azure-functions/functions-triggers-bindings.md#supported-bindings).
19
19
20
20
> [!NOTE]
21
-
> Currently, the Azure Cosmos DB trigger is supported for use with the SQL(Core) API only.
21
+
> Currently, the Azure Cosmos DB trigger is supported for use with the Core (SQL) API only.
22
22
23
23
## Requirements
24
24
25
25
To implement a serverless event-based flow, you need:
26
26
27
27
***The monitored container**: The monitored container is the Azure Cosmos container being monitored, and it stores the data from which the change feed is generated. Any inserts and changes (e.g., CRUD) to the monitored container are reflected in the change feed of the container.
28
-
***The lease container**: The lease container maintains state across multiple and dynamic serverless Azure Function instances and enables dynamic scaling. This lease container can be pre-created or automatically created by the Azure Cosmos DB Trigger, if you set the *CreateLeaseCollectionIfNotExists* flag in the [configuration](../azure-functions/functions-bindings-cosmosdb-v2.md#trigger---configuration). Partitioned lease containers are required to have a `/id` partition key definition.
28
+
***The lease container**: The lease container maintains state across multiple and dynamic serverless Azure Function instances and enables dynamic scaling. This lease container can be manually or automatically created by the Azure Cosmos DB Trigger.To automatically create the lease container, set the *CreateLeaseCollectionIfNotExists* flag in the [configuration](../azure-functions/functions-bindings-cosmosdb-v2.md#trigger---configuration). Partitioned lease containers are required to have a `/id` partition key definition.
29
29
30
30
## Creating your Azure Cosmos DB Trigger
31
31
@@ -35,7 +35,7 @@ Creating your Azure Function with an Azure Cosmos DB Trigger is now supported ac
35
35
*[Visual Studio Core Extension](https://code.visualstudio.com/tutorials/functions-extension/create-function) for Visual Studio Code users.
36
36
* And finally [Core CLI tooling](../azure-functions/functions-run-local.md#create-func) for a cross-platform IDE agnostic experience.
37
37
38
-
## Running your Azure Cosmos DB Trigger locally
38
+
## Run your Azure Cosmos DB Trigger locally
39
39
40
40
You can run your [Azure Function locally](../azure-functions/functions-develop-local.md) with the [Azure Cosmos DB Emulator](./local-emulator.md) to create and develop your serverless event-based flows without an Azure Subscription or incurring any costs.
0 commit comments