-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New feature idea: Using ABP on Azure CosmosDB with the MongoDB API #2465
Comments
Related: #386 |
Thank you @rlavaud for your feature and implementation suggestions. I agree on your idea in general and added it to backlog. Package name would be |
Hello @hikalkan sorry I can not see Volo.Abp.MongoDB.CosmosDB package |
hi @pramodbobde We haven't started yet. |
It's still in the roadmap. #2532 CosmosDB integration with EF Core and MongoDB API |
Hi all
I have been learning a lot about ABP via this forum and I started using it in an application idea that I have. One thing I want to do is being able to use Cosmos DB on azure which is compatible with the MongoDB api. Technically speaking you can use the mongodb module provided out of the box and it should work but the devil is in the details.
Here is where I run into issues:
Here is my feature idea
1 Create a new module Volo.Abp.CosmosDB which inherits from Volo.Abp.MongoDB
2 Add two new interfaces ITypedEntity and IPartitionedEntity
ITypedEntity will add a fields named Type
IPartitionedEntity will add a field named PartitionKey
ITypedEntity will hold a type name like 'User' or 'Order' etc to identify the type of entity pulled in the collection which multiple document type
IPartitionedEntity will have a value for the partition key to satisfy Cosmos DB
The new module would have a new ICosmosDBRepository which inherits from IMongoDBRepository to leverage existing mongo DB code as much as possible.
Is this a good idea or is this better left to each individual application to implement.
The text was updated successfully, but these errors were encountered: