SQL is 43 years old – Here’s why we still use it today
Been programming for 30+ years, and 99% of my projects use SQL databases.  I&#x27;ve tried and dropped NoSQL many times.  I still wake up in a cold sweat thinking about the earliest version of Firebase where I had a project that tried to join three tables together to get some meaningful data.<p>I still remember the response of a Firebase team member to my forum question about it - &quot;These days, storage and computing power is cheap - just duplicate the child table as nodes in the main table and do it all that way for every parent&#x2F;child relationship you have.  Don&#x27;t worry that you have to duplicate the same set of data for every parent that is related to the same child...That&#x27;s how NoSQL works...&quot; &lt;shudder&gt;<p>Even though I use ORMs in my project these days, every time I have to test a complex query, I write it in raw SQL first and check it before trying to make the ORM duplicate the same query.<p>Granted, NoSQL has its place and its advantages, but for me, when it comes to &quot;money code&quot;, I will stick to SQL.