InfoQ Homepage Presentations Core.logic and SQL Killed my ORM
Core.logic and SQL Killed my ORM
43:34
Summary
Craig Brozefsky presents the tradeoffs involved with moving to a purely SQL relational model, instead of using an ORM, along with some of the tools built to facilitate this.
Bio
Craig Brozefsky (@cbrozefsky) has been hacking lisp web apps since before the turn of the century, first in Common Lisp and now Clojure. He currently works for ThreatGRID Inc as a senior research engineer for their malware analysis and intelligence product.
About the conference
Clojure/West is the newest conference creation from Alex Miller (aka @puredanger). Alex has been running the Strange Loop conference in St. Louis since 2009, smashing together the worlds of functional and dynamic programming languages, concurrency, distributed systems, web and mobile. Since early 2010, Alex has also been part of a team using Clojure at Revelytix.
Aug 15, 2013
-
Related Sponsored Content
-
Related Sponsor
/filters:no_upscale()/sponsorship/topic/f1e73882-f385-4f4f-89e2-0799e364e183/CockroachRSB-1684221636780.jpg)
Community comments
Not a hater either
by Arturo Hernandez,
Not a hater either
by Arturo Hernandez,
Your message is awaiting moderation. Thank you for participating in the discussion.
For people like me that have used SQL for a very long time, is clear that the heroic effort of ORM writers has not been awarded with good results. I'd say that the biggest shortcoming of SQL technology is that it doesn't do the whole work. I mean SQL code is not only parsed/compiled but is decomposed, analyzed to produce an execution plan. When was the last time C++, Haskell or any language created an execution plan!? Never! Oracle goes so far as to statistically analyze my data and then deciding if an index does not have enough values to be useful. I don't think we need an ORM, we don't need to map, we need an "SQL extender". We need to write more code with less execution information, and in consequence we need more automatic execution planners. Something that we can write code and do statistical analysis on my network latency so it can decide what to reduce first. If I only had time!!!