Modeling Relational Data with Cosmos DB

[@chriscardoz]

Way too much redundancy and seems like a nightmare if I want to add features in the app later cause I need to rethink my documents schema and update the billions of documents before a production update.

[@wrod7]

how do you decide when to go nosql vs relational sql?

[@nodda4201]

This it merely my own opinion: I was wondering the same thing & found Cosmos is more work up front but it pays itself off if you are doing anything at scale across global regions, or if you are want to avoid things such as having to shard your data long term. It is just my opinion but I think Cosmos in particular is going to make SQL a legacy model by 2025 as people learn the best practices.

[@sau002]

Very good narration. I think the speaker is well versed with CosmosDB. However, the title of the Video of this misleading. Relational database systems have very strong foundations and the video appears to be sending the message that CosmosDB is the ultimate solution and will solve the problems of SQL. While it does have some strengths over MSSQL - it is premature to present Cosmos DB as an entire replacement for MSSQL or any other RDBMS. I have strong objection to anybody who takes a position "either SQL or NoSQL" - I am of the opinion that both have a role to play. I am sad and alarmed.

[@wuzixiao1]

As a user of both of them, I agree with you. Cosmos db is good at unstable schema scenarios, but you will have some redundant data. Sql data is normalized but a bit hard to change schema

[@lee45283]

He’s on a Mac and not a surface book thing!