Data Modeling and Partitioning in Azure Cosmos DB - Mark Brown - NDC Oslo 2021

The era of cloud computing has ushered in a new era where applications now demand unprecedented levels of scale and size. Relational databases which have been with us for 50 years are often not able to handle ingesting hundreds of MB a second or growing to PB in size. Enter NoSQL databases which were designed specifically to deal with these unique challenges.

In this session we will take a simple e-commerce application and migrate it from a relational database to a partitioned, NoSQL database. Along the way you will learn how to analyze you application to uncover how to design you data model and how to measure your application's performance as you iterate and test your designs. You will learn the tips, tricks and techniques for modeling and partitioning data that will allow your application to grow to unlimited scale and size with millisecond response times.

Check out more of our featured speakers and talks at

[techwithdebrah]

Embedding tags inside the product document. What if the same tags will be used for multiple other products and we won't to update the tag name ?

[FilipCordas]

Something I don't understand about "No-SQL" databases is you model your database in this way on a regular SQL database will there be any performance improvements at all. On TechEmpower mongoDB is below postgresql because you run simple queries like get by indexed id. If you denormalize, don't guarantee acid, can't do joins, have to correctly partition before you start working, can't do partial entity updates why use a database a database at all. In fact if you store dynamic objects and not strongly defined structures it can theoretically only be slower because you need more pointer jumps.

[ranjansrivastava]

Dear Sir, Very nice video !!! I have one question Can we create partition key on high cardinality column (id) like you discussed on the customer container. Please share your thoughts.