Different tools designed for different needs. I still like the referential integrity offered by RDBMs but I understand the potential performance advantages from NoSQL DBs but each project is different. The needs of an e-commerce startup are vastly different than a fortune 500 company in the fintech sector. Of course many people fall into the trap of assuming you have to pick just one. There are times an organization may want to use both depending on your workflow and use cases.
Based on the date of the video I hope it's not an april fools joke :D but overall i think there is a tradeoff for databases like mongo db with a need on a user's side to take care of consistency of duplicated data. I only really have real life experience with sql databases though. Do you think that in our current age should mongo db be the "default" options when choosing a database for a new project?
This is not a joke and I repeatedly said SQL is awesome. The point of the video is just to give NoSQL a try. It takes a little bit of time to get used to it because it's not a relational database. No tables, no triggers, no foreign keys etc. All you have are documents. Plain-old JSON documents - but these are much closer to how you store and use data in your app. This one is very important. It means that you don't need to run circles around your tables anymore. Forget normalization. Forget complex JOIN selects. A document is a document. This also means you need to handle things like data duplication across documents and curse at the documentation that something trivial in SQL just isn't there in NoSQL. I think you should give it a try. Once you go over that initial shock I believe you'll likely learn to appreciate NoSQL. Finally, I believe NoSQL should be the default option for storage. This is a hot take, I know. But having used SQL for 15 years and NoSQL for only 3 - I'd never start a new project with anything other than document stores again.
Different tools designed for different needs. I still like the referential integrity offered by RDBMs but I understand the potential performance advantages from NoSQL DBs but each project is different. The needs of an e-commerce startup are vastly different than a fortune 500 company in the fintech sector. Of course many people fall into the trap of assuming you have to pick just one. There are times an organization may want to use both depending on your workflow and use cases.
Based on the date of the video I hope it's not an april fools joke :D but overall i think there is a tradeoff for databases like mongo db with a need on a user's side to take care of consistency of duplicated data. I only really have real life experience with sql databases though. Do you think that in our current age should mongo db be the "default" options when choosing a database for a new project?
This is not a joke and I repeatedly said SQL is awesome.
The point of the video is just to give NoSQL a try. It takes a little bit of time to get used to it because it's not a relational database. No tables, no triggers, no foreign keys etc. All you have are documents. Plain-old JSON documents - but these are much closer to how you store and use data in your app.
This one is very important. It means that you don't need to run circles around your tables anymore. Forget normalization. Forget complex JOIN selects. A document is a document.
This also means you need to handle things like data duplication across documents and curse at the documentation that something trivial in SQL just isn't there in NoSQL.
I think you should give it a try. Once you go over that initial shock I believe you'll likely learn to appreciate NoSQL.
Finally, I believe NoSQL should be the default option for storage. This is a hot take, I know. But having used SQL for 15 years and NoSQL for only 3 - I'd never start a new project with anything other than document stores again.