Re: Spring/hibernate and JDBC
On Jul 9, 5:32 pm, Jack <junw2...@gmail.com> wrote:
On Jul 9, 4:01 pm, markspace <-@.> wrote:
On 7/9/2011 2:56 PM, Jack wrote:
With spring and hibernate so popular now, is there anybody still only
use JDBC to write database application code? Thanks.
I'm sure someone is, but yes I assume that JPA & Hibernate and
dependency injection frameworks like Spring and JSF have become the nor=
m.
Still good to know what JDBC is and does, since it's used by JPA and
Hibernate (et al.).
Is using JDBC to access database more efficient than using
Spring/hibernate?
Yes and no. It can be more efficient as a programmer to use Hibernate
(but don't use Spring!), at least if you stay with the JPA-compliant
parts of Hibernate. It can run more efficiently to use JDBC without
JPA, but usually is not.
Unfortunately, most use of Hibernate in the wild is quite ignorant and
harms the respective projects. I have yet to encounter intelligent
use of Spring in a real project.
Good use of JPA will make your program quite clean and maintainable,
i.e., very efficient in the development and maintenance dimensions.
Bad use of JPA, like bad use of a chain saw, results in a horror-movie
scenario. For certain bulk operations, JDBC is better.
Asking about "efficiency" for use of JPA vs. JDBC calls is like asking
if it's more efficient to use an automobile than a bicycle. The use
cases differ, so where one is more appropriate the other is less so,
and "efficiency" has little to nothing to do with it. That is to say,
"efficiency with respect to what?" is your real question.
So, efficiency with respect to what?
Use JPA when you want to code to an object model that persists itself,
without regard for the data-centric point of view. Use JDBC when you
need a relational model of your persistent data.
Eschew Spring.
--
Lew