@chanakya@social.screamingatmyscreen.com
Post #2445501
2023-09-22 13:55 UTC
Replies (2)
-
@chrisg@fosstodon.org 2023-09-22 14:00
@chanakya@social.screamingatmyscreen.com To be clear - I don't think there is anything wrong, per se, with SQL. Works fine, will continue working fine, I don't see it going anywhere like the network model, for example. But it is a product of the 70s, where physical proximity of data on disk meant different things than it does today. When you executed on a single CPU, with much more expensive cycles. Does it work today? Yes. Can we do better, with a redesigned model? Also yes. (Did NoSQL achieve this? I think not)
-
@chrisg@fosstodon.org 2023-09-22 14:05
@chanakya@social.screamingatmyscreen.com As for its current dominance. The relational model was an out-of-this-world invention. It rightfully took everything by storm. That's why it dominates today, there has been nothing better _as a product_ around. Models? Meh, maybe. Docs + key/value are too simple, graphs too hard. So as long as nothing new challenges SQL, it's a nice middle ground that keeps incrementally being improved. With an immense ecosystem, from tools to uni courses, of course it's not going anywhere.