Question

An e-commerce platform stores Customers and Orders in separate Azure Cosmos DB for NoSQL containers. When a customer record is soft-deleted (a 'deleted' flag set to true), the business requires that all of that customer's orders be automatically marked as orphaned within seconds, without impacting the write latency of the customer-facing application. Which approach best satisfies this requirement?

Accepted Answer

Deploy an Azure Function with a Cosmos DB trigger on the Customers container that reacts to change feed events and updates the related orders in the Orders container.

Answer

Add a post-trigger to the Customers container that queries and updates all matching order documents in the Orders container within the same operation.

Answer

Enable Azure Synapse Link on the Customers container and run a nightly Spark job to reconcile orphaned orders in the analytical store.

Answer

Configure a stored procedure on the Customers container that transactionally updates both the customer and all their orders in a single batch.