Most "programmers" just can't understand relational databases and SQL. It's too hard.

I've seen things you wouldn't believe. Random deadlocks in multi-billion transaction reporting systems. Atomic transactions split into multiple commits in banking applications. Copying rows between tables instead of setting a flag on a row. All because highly paid programmers are scared of RDBs.

I've had the same experience (over decades) and never understood it. SQL should not be difficult for any professional programmer, and it's extremely powerful.

> All because highly paid programmers are scared of RDBs.

Really? That's not my experience over the last thirty years of programming. As soon as relational databases became something that everyone could use we all jumped in And not just programmers either, a lot of people who never wrote a line of code in their lives became adept at writing SQL in order to get around limitations in ERP systems for instance.

Is this problem something that afflicts only younger programmers?

All those strong relations will be lost, like tears in the rain.

Thank you for noticing.

I've got some developer PTSD from a previous project where the solution architect decided to use CosmosDB for the entire domain model that was very relational and very transactional, all because "NoSQL is easy to learn and allows rapid development".

Yeah it is, until you're trying to manually create and maintain relations between documents in different schemas owned by different microservices.

I've read this again and again in this forum and other dev communities, so I didn't hesitate. I can't say I love SQL, but it's not that bad, Databases look interesting to me.