> What would replace SQL? An API of course! Turtles all the way down. At some point you have to use some sort of data access language. Providing an API instea

> What would replace SQL? An API of course! Turtles all the way down. At some point you have to use some sort of data access language. Providing an API instead of using SQL queries only works if you have a fairly limited number of different procedures to be called and data structures to be returned. Otherwise you'll end up with a combinatorial explosion of API methods and input values. If you view your SQL database as mere data storage that approach could be valid. If however, you're working with complex relational models and data processing providing an API is a pointless endeavour. I've seen (legitimate, mind you) SQL queries which were more than a hundred lines long and in turn called multiple additional embedded queries. Some of those queries used groups and window functions alongside with normal tabular data. Good luck with providing that as an API!