Skip to content

Commit 170fdce

Browse files
author
Matias Quaranta
committed
Addressing more comments
1 parent 799a4c8 commit 170fdce

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/cosmos-db/change-feed-functions.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,21 +11,21 @@ ms.reviewer: sngun
1111

1212
# Serverless event-based architectures with Azure Cosmos DB and Azure Functions
1313

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.
1515

1616
![Serverless event-based Functions working with the Azure Cosmos DB Trigger](./media/change-feed-functions/functions.png)
1717

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).
1919

2020
> [!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.
2222
2323
## Requirements
2424

2525
To implement a serverless event-based flow, you need:
2626

2727
* **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.
2929

3030
## Creating your Azure Cosmos DB Trigger
3131

@@ -35,7 +35,7 @@ Creating your Azure Function with an Azure Cosmos DB Trigger is now supported ac
3535
* [Visual Studio Core Extension](https://code.visualstudio.com/tutorials/functions-extension/create-function) for Visual Studio Code users.
3636
* And finally [Core CLI tooling](../azure-functions/functions-run-local.md#create-func) for a cross-platform IDE agnostic experience.
3737

38-
## Running your Azure Cosmos DB Trigger locally
38+
## Run your Azure Cosmos DB Trigger locally
3939

4040
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.
4141

0 commit comments

Comments
 (0)