Data Modeling and Partitioning in Azure Cosmos DB

[@slavengaspar6859]

An excellent presentation, with an excellent style and measure. It is not too architecturally abstract, but it also does not delve deeply into the program code. Great choice of examples! It can serve as an excellent foundation or starting point for designing a large number of different applications.”

[@AzureCosmosDB]

If you'd like to get into the code for this, take a look at this GitHub repository here. github.com/AzureCosmosDB/CosmicWorks Hope this helps.

[@hansrudolf5849]

Amazing presentation - a shame that this will probably get burried by some KZbin algorithm and never see the daylight ...

[@mrjamiebowman1337]

his videos on Plural Sight are really good.

[@AzureCosmosDB]

I agree! He does an incredible job helping train developers!

[@suniguha]

Excellent presentation

[@chetan2309]

Thanks for this CosmosDb team and Lenni. The only thing that is missing is how to select the right API. Core vs MOngoDB?

[@AzureCosmosDB]

Hello. We're glad you enjoyed the presentation! There are a number of factors to consider when selecting one of the APIs provided by Azure Cosmos DB. You'll need to answer "is this a new project, or am I migrating something to Cosmos DB?" Let's say your development team is already well versed in MongoDB and has an application using a particular driver, this may lead you to using MongoDB. You can read more on this subject by going to this doc that has a great video that explains more. learn.microsoft.com/azure/cosmos-db/choose-api

[@mrkyaing5456]

Thanks Sir, it helps me a lot .

another query for the sales orders could be : which products sell the best.

[@salman1277]

real helpful to improve

[@alonerock136]

thanks, its helpful

[@itamareduardo]

Amazing talk!

[@anasw6432]

Each Micro service has its own database/container, I think the question is invalid from its concept to Microservice

[@JueliLin-s8j]

Micro service design

[@georgeollis]

Amazing presentation

[@slavengaspar6859]

Excellent presentation