Sorry, nothing personal, but just saying "NoSQL" we don't say anything :)
And if the post is about Azure Cosmos DB, then it's better call it so :) It is not about NoSQL in general, right - rather about specific storage service...
While relational databases are less or more alike, various NoSQL storages are all quite different and with different goals. Often it is about "P" part of CAP-theorem.
There was a hype about NoSQL in recent years, but now it seems to be somewhat subsided. Meanwhile both MySQL and Postgres nowadays can store and process JSON data which makes them "relational databases with NoSQL features".
General rule of thumb for me is don't try substituting relational DB with some "innovative" NoSQL engine just out of curiosity. Unless it is the part which could be easily redesigned and migrated in future if anything goes wrong. Because we all need to learn, surely.
Exactly! Relational databases solve many more problems than just the cost of storage. And the newer databases also provide functionalities that let you partition data. Both NoSQL and relational databases have their pros and cons that need to be weighed for each application. Naively choosing one over the other can get one in trouble as the application matures.
Fair point. I didn't mean to assert that relational databases are irrelevant, but rather that one of the reasons why we normalized data to begin with has fundamentally shifted.
That said - you're absolutely right. Each has its distinct advantages.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Friend!
Sorry, nothing personal, but just saying "NoSQL" we don't say anything :)
And if the post is about Azure Cosmos DB, then it's better call it so :) It is not about NoSQL in general, right - rather about specific storage service...
While relational databases are less or more alike, various NoSQL storages are all quite different and with different goals. Often it is about "P" part of CAP-theorem.
There was a hype about NoSQL in recent years, but now it seems to be somewhat subsided. Meanwhile both MySQL and Postgres nowadays can store and process JSON data which makes them "relational databases with NoSQL features".
General rule of thumb for me is don't try substituting relational DB with some "innovative" NoSQL engine just out of curiosity. Unless it is the part which could be easily redesigned and migrated in future if anything goes wrong. Because we all need to learn, surely.
Exactly! Relational databases solve many more problems than just the cost of storage. And the newer databases also provide functionalities that let you partition data. Both NoSQL and relational databases have their pros and cons that need to be weighed for each application. Naively choosing one over the other can get one in trouble as the application matures.
Fair point. I didn't mean to assert that relational databases are irrelevant, but rather that one of the reasons why we normalized data to begin with has fundamentally shifted.
That said - you're absolutely right. Each has its distinct advantages.