We use JDBI @Truecaller together with Metrics library. Not only it is clean and tidy, it also gives you immediate profiling around your database calls. This is priceless in a big service oriented environment. With it, you can exactly see the rate of happening (mean/last 1/5/15 minutes average) and latency (mean/avg/std-dev/75/95/98/99/99,9percentiles) for each database query. I wouldn't want to go back to manual logging and optimization hell. JDBI+Metrics opens a totally new dimension to your monitoring/profiling/optimization!

A second shoutout for JDBI. I don't attempt to use it for anything fancy, but it hides a lot of the JDBI boilerplate in a very sane way.

Cheers mate! That createQuery() call looks to be exactly what I need (query safety on a low level JDBC stream object).