That's another thing I will never understand: Back in the days (1998), we used an Object Store (*nix version of NeoAccess, in our case)
In the following years it turned out everyone else insisted on keeping SQL around, and so we had to turn to manual SQL wrapping again (we created code generators, because it's too error-prone and boring to do manually) until ORM came around, which IMHO is a totally ass-backward way of dealing with a DB from an OO point-of-view. Also, clients demanded that we run stuff in J2EE containers and hence, that we write it in Java, which I still consider to have been a marketing exercise by Sun Microsystems to obtain more broad meaning for their ailing Spark CPU line (Java has always ran suspiciously better on *nix than any other platform). Little did they count on GNU/Linux taking over the server universe. We did go Java, but never liked it, and still consider it the result of brainwashing, and don't understand the need for all those extra layers. There is not one thing that the container does that the OS cannot do better, except packaging, and ever there, J2EE is "write once, debug everywhere" in the field and therefore of little real help. Since then, other enviroments and languages came along, all with their strengths and weaknessess, but all with a common goal, from my POV, which is to make development more abstract, less error-prone, more specialized, easier to package and deploy etc.. and to take up a lot of extra CPU power and memory. I don't believe in making development easier: It resulted in the extremely dangerous monsters that are online, written in PHP by good-intentioned dilattantes with an excellent grasp of their fields but with little development skills. Same in Java, same in Python, same in Ruby.. While these are all interesting languages with interesting frameworks, they do not, IMHO contribute anyhting new except runtime inefficiency, and some extra layers to make debugging harder.
Moore's law saved our bacons, there, because as time progressed, everything became more inefficient, but everyone had bigger CPU's and a lot of RAM to be able to keep up.
So you see, for me, the current situation with the traction of NoSQL and the immense opportunily (and necessity, IMHO) to make the server-side efficient and lean again (power is now a major cost in the data center, vs bandwidth) is really a lot of "back to the future".