File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes JPA or JDBC Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "JPA or JDBC" Watch "JPA or JDBC" New topic


ankur rathi
Ranch Hand

Joined: Oct 11, 2004
Posts: 3830
What would you choose for what kind of project? JPA or JDBC?

arvin ramon
Ranch Hand

Joined: Oct 04, 2007
Posts: 31
If a project needs faster database access and all it is doing is straight updates to database, going against jdbc and doing batch updates are faster.

On the other hand, if you are frequently accessing data and need a layer to cache data, I would personally prefer JPA or any other OR layer.
Mladen Grabowsky

Joined: Sep 19, 2007
Posts: 29
Personally, if i wouldn't go for JPA/Hibernate, i'd prefer iBatis over plain JDBC.
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper

Joined: Aug 26, 2006
Posts: 4968

The question can almost be generalized to "when should you use a framework, and when shouldn't you?"

Simple and straight forward apps probably don't need a framework. As things get more complicated, and management of the application over time and change becomes more important, a framework, like JDO or hibernate, becomes more and more helpful.

-Cameron McKenzie
kaizen liu

Joined: Mar 15, 2005
Posts: 2
i will give diffent answer in diffent situatiion,for example,maybe some small and simple project i will choose ibatis or jdbc,big but not enough i think jpa will work well,and big project i think hibernate is a good choice
Victor Maehira
Ranch Hand

Joined: Mar 08, 2007
Posts: 37
Besides performance, I would take into account the database model. Mainly in legacy databases, you may find unnormalized tables, poor referential integrity and other aberrations that JPA does not fit. If you choose JPA in these cases, you will probably solve problems coding SQL queries instead of taking advantage of the framework.
I agree. Here's the link:
subject: JPA or JDBC
It's not a secret anymore!