Re:How and why the Relational Model works for databases
by oblio on Monday January 17, 2022 @06:01AM
(#29965349)
There you go, I've edited my previous comment to account for pedantry.
Re:How and why the Relational Model works for databases
by LAC-Tech on Monday January 17, 2022 @04:58PM
(#29972157)
I guess I should just accept the term that "NoSQL" now pretty much means "Monngo and Dynamo". Because it feels weird to group key-value stores, columnar stores and graph DBs under one term.
Re:How and why the Relational Model works for databases
by oblio on Monday January 17, 2022 @05:43PM
(#29972544)
Well, I don't want to be super mean to you or NoSQL, but NoSQL itself was a bit of a fad.
Columnar stores and graph DBs have always felt more like "real" tech, something promoted for specific use cases.
Key-value stores I'm not even going to be denigrating at all since we've had them since forever and they do a great job at their tasks (BerkeleyDB, Memcache, Redis, etc.). They don't deserve being included into fads or niches, they're a very valuable universal resource.
At least that's how I see it.
Re:How and why the Relational Model works for databases
by LAC-Tech on Monday January 17, 2022 @07:14PM
(#29973238)
Yeah but in my mind columnar stores and graph stores are NoSQL databases. Because they're not relational.
But the term has shifted underneath me. NoSQL means document database.
And - in practice - it means using a document database as the primary store when it's not really the right choice (been there!)
Impressive!