Also, IMO again, relationships can be anywhere, only just managed directly by the database or not.
I personally equate NoSQL to newer databases, created anew from scratch, rather than relying on SQL structure; and tried to solve problems (which can actually be unsuccessful, but marketeers won't let you know, if possible). So I do know there are multiple types. And NoSQL can also be ACID-guaranteed.
Not that the old technology, SQL, aren't getting updated. It is just not remade from scratch, that's all.
IMO, it is more of relying on cutting edge technology, or a stable technology. Again, "being made for the purpose" can fail. Only what can make sure for me are either, successful cases, or tech / liability support.
I totally agree with the statement that SQL is older and there was no improvement for a longer time.
If we look at MongoDB, they released support for multi-document transactions in 2018. So the debate of using MongoDB vs an SQL DB specifically could be a nice topic to discuss. But still, we should focus on use cases and not performance comparison.
A database isn't programming-language specific, but everything else from drivers, to programming, to maintenance, are.
Otherwise, I could be wrong. I have little experience with NoSQL. NoSQL is the path less people take, and I am just advised against taking...
Also, IMO again, relationships can be anywhere, only just managed directly by the database or not.
I personally equate NoSQL to newer databases, created anew from scratch, rather than relying on SQL structure; and tried to solve problems (which can actually be unsuccessful, but marketeers won't let you know, if possible). So I do know there are multiple types. And NoSQL can also be ACID-guaranteed.
Not that the old technology, SQL, aren't getting updated. It is just not remade from scratch, that's all.
IMO, it is more of relying on cutting edge technology, or a stable technology. Again, "being made for the purpose" can fail. Only what can make sure for me are either, successful cases, or tech / liability support.
I totally agree with the statement that SQL is older and there was no improvement for a longer time.
If we look at MongoDB, they released support for multi-document transactions in 2018. So the debate of using MongoDB vs an SQL DB specifically could be a nice topic to discuss. But still, we should focus on use cases and not performance comparison.
MongoDB specifically, vs SQL (mentioned PostGRES) are discussed here.
PostgreSQL vs MongoDB
Ben Halpern ・ May 28 ・ 1 min read
Personally, I see MongoDB transactions as not yet in place, and lacking named SAVEPOINTs. And sometimes that matters a lot.
Thanks for that. I will read it ;)