Why Should I Prefer Jdbi Over Hibernate?

1.	Why Should I Prefer Jdbi Over Hibernate?
Answer» There are couple of reasons why should you prefer it over HIBERNATE: You don’t NEED to worry about lazy/eager fetching and how that is going to affect your query time on large data sets. You know exactly what SQL is going to be executed to acquire the data you are requesting. With Hibernate, you can sometimes have to do a lot of messing around with HQL and configuring your objects to what you intended to have returned. You ultimately resort to SQL, but then have the DIFFICULTLY of properly mapping your results back to your domain objects, or you give up and allow hibernate to fetch them one by one. Mappings aren’t complicated because you manage them on your own and you don’t have to rely on getting the right combinations of annotations and optimizations. There are couple of reasons why should you prefer it over Hibernate:

Answer»

There are couple of reasons why should you prefer it over HIBERNATE:

You don’t NEED to worry about lazy/eager fetching and how that is going to affect your query time on large data sets.
You know exactly what SQL is going to be executed to acquire the data you are requesting. With Hibernate, you can sometimes have to do a lot of messing around with HQL and configuring your objects to what you intended to have returned. You ultimately resort to SQL, but then have the DIFFICULTLY of properly mapping your results back to your domain objects, or you give up and allow hibernate to fetch them one by one.
Mappings aren’t complicated because you manage them on your own and you don’t have to rely on getting the right combinations of annotations and optimizations.

There are couple of reasons why should you prefer it over Hibernate:

Discussion