You are developing a solution that will use a multi-partitioned Azure Cosmos DB database. You plan to use the latest Azure Cosmos DB SDK for development. The solution must meet the following requireme

Question

Options

• ACreate an Azure App Service API and implement the change feed estimator of the SDK. Scale
• BCreate a background job in an Azure Kubernetes Service and implement the change feed feature
• CCreate an Azure Function to use a trigger for Azure Cosmos DB. Configure the trigger to connect
• DCreate an Azure Function that uses a FeedIterator object that processes the change feed by

• A
  17% (5)
• B
  7% (2)
• C
  76% (22)

Explanation

Azure Functions is the simplest option if you are just getting started using the change feed. Due to its simplicity, it is also the recommended option for most change feed use cases. When you create an Azure Functions trigger for Azure Cosmos DB, you select the container to connect, and the Azure Function gets triggered whenever there is a change in the container. Because Azure Functions uses the change feed processor behind the scenes, it automatically parallelizes change processing across your container's partitions. Note: You can work with change feed using the following options: - Using change feed with Azure Functions - Using change feed with change feed processor https://docs.microsoft.com/en-us/azure/cosmos-db/read-change-feed#azure-functions https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed-pull-model#using-feedrange-for-

No community discussion yet for this question.