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.
We have reviewed this and have elected to not include this on our road map for the time being. We may revisit this in the future so will leave as unplanned rather than declined or closed.
Thanks for your suggestion and comments.
This would be real handy and would address a number of concerns.
There is no update on this to report. When there is progress we will definitely update here.
Any update on this?
Sean Feldman commented
There's an effort to consolidate and improve tracking of the Azure services events in a public repository https://weblogs.asp.net/sfeldman/azure-events-wishlist. Feel free to add this event there.
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.
Sylvain Pontoreau commented
Definitively a feature we need in CosmosDB for a lot of scenario (Event Sourcing is the first one of course)
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
Would make CosmosDB the perfect solution for event sourcing architectures...
Stan Spotts commented
"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.
Lukas Jung commented
Any updates on this?
Would be a very helpful feature...
It would be great if we could easily add an azure CosmosDB as an event publisher so we can get informed about new, updated or deleted documents, edges, collections etc.
What is the status of this? Would be indeed a good idea
Tobias Weisserth commented
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.