EventFlow icon indicating copy to clipboard operation
EventFlow copied to clipboard

Azure Cosmos DB support

Open Ilchuk-Mihail opened this issue 7 years ago • 7 comments

Ilchuk-Mihail avatar Jun 07 '18 11:06 Ilchuk-Mihail

@Ilchuk-Mihail Nothing yet

rasmus avatar Jun 07 '18 12:06 rasmus

@rasmus I found. We can start with using this https://docs.microsoft.com/en-us/azure/cosmos-db/mongodb-introduction Azure Cosmos DB has support of Mongo DB API :)

Ilchuk-Mihail avatar Jun 07 '18 13:06 Ilchuk-Mihail

One downside to using CosmosDB via the Mongo API vs. the DocumentDB api is that you lose support for reading from the Cosmos Change Feed.

Perhaps https://github.com/ASOS/SimpleEventStore would be a good starting place for adding cosmosdb support?

jasonchester avatar Jun 07 '18 17:06 jasonchester

Maybe use the Docker version for integration testing

rasmus avatar Jun 07 '18 18:06 rasmus

There currently no plans for adding Azure Cosmos DB

/rasmus

On Mon, Aug 12, 2019 at 8:13 AM Anthony Hocquet [email protected] wrote:

Is there any plan in the near futur to support Cosmos DB ? I'm about to start a new project in the company I work for, so I'm wondering if I should setup an Azure SQL Server or wait a little bit and stick with Cosmos DB.

Thank you :)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/eventflow/EventFlow/issues/478?email_source=notifications&email_token=AAAEUDFQABYCHG6WKXY65V3QED5RPA5CNFSM4FDZAWQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4BUNXY#issuecomment-520308447, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAEUDDBYBNQV7ZFKTYUAO3QED5RPANCNFSM4FDZAWQQ .

rasmus avatar Aug 13 '19 11:08 rasmus

As someone who as spent significant time implementing and tuning CosmosDb support for another system with CosmosDb Event Storage (Equinox), I'd strongly advise against considering a 'trivial' event-as-a-document implementation - while it will work, and the change feed is nice, ultimately you won't get a viable mix of semantics, perf and cost effectiveness without a heck of a lot of engineering effort, necessitating surfacing some necessary implications of applying Cost Model Sympathy (and doing so would duplicate the purpose of CosmoStore, SimpleEventStore, Eveneum, which are already non-trivial efforts)

bartelink avatar Aug 13 '19 14:08 bartelink

I was able to implement Eveneum as the interface to CosmosDB pretty easily actually. I am not sure if that is the direction you want to go here in EventFlow but it is definitely an option. The only real issue with using Eveneum is there is a name clash as both use EventStore as a concept.

jessemillerrev avatar Aug 09 '22 18:08 jessemillerrev

Hello there!

We hope you are doing well. We noticed that this issue has not seen any activity in the past 90 days. We consider this issue to be stale and will be closing it within the next seven days.

If you still require assistance with this issue, please feel free to reopen it or create a new issue.

Thank you for your understanding and cooperation.

Best regards, EventFlow

github-actions[bot] avatar Apr 08 '23 13:04 github-actions[bot]

Hello there!

This issue has been closed due to inactivity for seven days. If you believe this issue still needs attention, please feel free to open a new issue or comment on this one to request its reopening.

Thank you for your contribution to this repository.

Best regards, EventFlow

github-actions[bot] avatar Apr 16 '23 09:04 github-actions[bot]