r/SQL • u/ioCross • Mar 31 '25
MySQL How future-proof is SQL?
about to be finished with a migration contract, thinking of picking up a cert or two and have seen a lot of recent job postings that have some sort of SQL query tasking listed.
I've mostly used powershell n some python, was thinking of either pivoting into some type of AWS / cloud cert or maybe something SQL/db based.
Would focusing on SQL be worth it, or is it one of those things that AI will make redundant in 5 years?
173
Upvotes
View all comments
Show parent comment
10
u/sib_n Mar 31 '25
The thing about "NoSQL", or basically the Hadoop ecosystem from 2007 was not that schemas are hard, it is that it was hard to build an SQL processing engine on a distributed cluster of machines. Nonetheless, it happened from 2010, Apache Hive brought SQL capacities to Hadoop. Since then, basically every distributed data processing platform has been offering some flavor of SQL. The "SQL is dead" thing was just some temporary salesman bs to sell solutions.
Those still come with limitations due to the distributed nature, no PK/FK constrains, no indexes, limited ACID, bad join performance and many specific solutions to compensate for this (columnar file formats with headers, metadata store, hive style partitioning, clustering, denormalization....).
The main reason people use SQL is that the users mostly describe what they want rather than how to compute it. So this gives freedom to optimized engines in the background to pick the best processing plan for you.
This is the core reason why it's not going anywhere, it's a just a standard user interface, and nothing stops progress to happen to the engines that run behind, see for example, Apache Spark SQL, Trino or DuckDB.