I remember a good 4-5 years where developers all around me were using couchdb, mongodb, and a host of others. mostly json in <-> json out kind of systems. And VERY hard to maintain after the initial TODO. I remember so much debugging and finding out old records didnt have a way to deal with changes in the "tables" or equivalents. It was maddening.

Dont get me wrong, it did create some really awesome specialty tools but you cant really get around ACID compliance when dealing with databases.

I think SQL has some awesome properties that keep it going:

Most major distributions are rock solid stable.
Its optimized and fast for data.
Its understandable to many types of industries. Software development is only the start.
Its integrated with everything already. So ODBCs can just plug and play most of the time.
Its the devil we know. ACID, transactions, etc... are all things we know about and are proven to work very well. Definitly when you need to MAKE SURE a thing made its way into the system.

[–] Valmond@lemmy.world 5 points 20 hours ago

Yeah 100% with you, had this mongo database where the first entry was like a description, the nr 2 and on the actual data. I mean if there were a description... Sometes 2 descriptions...

Why oh why.

And for sure SQL is kind of the cement of DB today, don't get me wrong, I like that what I learned yesterday actually still works, I'm just pondering the fact that it is so.

Maybe SQL isn't the hip language so people doesn't try to reinvent it all the time 😁