jOOQ is great. It brings a lot: * auto-complete in your IDE when writing queries in jOOQs Java DSL that maps quite naturally to SQL * type safety. e.g.: migra

jOOQ is great. It brings a lot: * auto-complete in your IDE when writing queries in jOOQs Java DSL that maps quite naturally to SQL * type safety. e.g.: migrate after a schema change, re-generate your jOOQ lib and see in your IDE (red underlines) all the place your queries would break using the new schema * build queries from parts (e.g.: store/manipulate some where clauses in a local variable) w/o any string manipulation But is has costs: * generate the jOOQ library from your schema at build time (or everytime the schema changes): increase build time (a little) and complexity (a db needs to be around during builds) * very small runtime overhead: queries are build at runtime * one more thing to learn To me the benefits outweigh the costs (unlike Hibernate, I much agree with the article) and I consider it similar to LINQ on C# while not being some language built in feature with it's own syntax.