I'm always looking for the best way to incorporate data access into our projects. JDBC gives me the most flexibility but is quite verbose and tedious to work with.

Hibernate and other ORMs are seem to work great...until I run into that one wierd issue or badly performing query that pretty much eats up any productivity I may have gained by using the abstraction. I also find it difficult to get more than standard CRUD tasks done using hibernate.

I have not used JDBI extensively and have only setup a small test project utilizing it(via dropwizard). This library seems like a great intermediate between JDBC and Hibernate.
* Does anyone else have experience using JDBI(either on its own or with dropwizard) in medium-large projects with a team?
* When you get further down the line or get into complex things, do you end up fighting the framework more than its helping? (like hibernate IMO, at least for me) * Anyone running JDBI in production, and is performance good?