How can we improve Azure Cosmos DB?

EventGrid publisher for CosmosDB

Instead of, or in addition to, the existing ChangeFeed please publish changes to Event Grid.

This shud be mngt ops like DB create, collection create etc.
AND changes to documents, including deletes.

119 votes
Sign in
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
ryan shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Password icon
Signed in as (Sign out)
  • Anonymous commented  ·   ·  Flag as inappropriate

    Agree would make cosmos viable in low latency situations for event sourcing. Using the ChangeFeed is difficult for low latency since it drives to cost up turning the polling interval up. Batches and error processing are also painful.

  • Rashun commented  ·   ·  Flag as inappropriate

    Are there any work arounds at least. Functions are great, the Cosmo add requires an extra step, adding another output to force the CosmoDb Binding Installer? But for quick prototyping Logic Apps is the way to go

  • Stan Spotts commented  ·   ·  Flag as inappropriate

    "We are working to deliver many more event sources and destinations later this year, including Azure Active Directory, API Management, IoT Hub, Service Bus, Azure Data Lake Store, Azure Cosmos DB, Azure Data Factory, and Storage Queues." -- Corey Sanders, August 16, 2017

    So this changed?

    It's very difficult to use Cosmos DB in a validadated (regulated) system since Change Feed doesn't let us ensure that every data change can be tracked for auditing needs. At least with the Event Hub, if the provider is set up to publish every changed element in a document, we could satisfy compliance issues.

  • Tobias Weisserth commented  ·   ·  Flag as inappropriate

    In addition it would maybe be useful to also subscribe to events based on particular tables, columns or fields in a document with enough information in the event to implement alerts based on value changes and such. Just an idea.

Feedback and Knowledge Base