Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

HIBERNET

 
MARIO DAVILA
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Its posible the use of hibernet in batch procesing in a aplication(not web)?,in such case which is the specification that i had to look for?
 
Halcon Guatemala
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Can you provide additional info about your problem? Thanks
 
Mark Spritzler
ranger
Sheriff
Posts: 17278
6
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hibernate and JPA can do mass updates/inserts/deletes, but you need to be careful that you either use the underlying JDBC Connection directly, or the new ways to do them, you will need to look at the APIs to get that.

Also, in terms of JDBC Batch processing, all Hibernate flushes occur using JDBC Batch processing.

Mark
 
MARIO DAVILA
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Mark Spritzler:
Hibernate and JPA can do mass updates/inserts/deletes, but you need to be careful that you either use the underlying JDBC Connection directly, or the new ways to do them, you will need to look at the APIs to get that.

Also, in terms of JDBC Batch processing, all Hibernate flushes occur using JDBC Batch processing.

Mark


thanks Mark .Im using unix whit db2 Do you think that a java aplication whit hibernet would have a good performanse against cobol?
 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by MARIO DAVILA:
Do you think that a java application whit hibernate would have a good performance against Cobol?


That is a difficult question to answer. However it is likely that the Cobol implementation could out-perform the Java/Hibernate combination. But even if that us is true - it still would be difficult to predict how much slower the Java/Hibernate combo actually would be. This is also heavily influenced by how good the designs of the both the Cobol and Java/Hibernate implementations are.

The only way to find out is to select a processing and I/O intensive sub-function of the existing implementation and to implement it in Java/Hibernate and compare the respective performances.

However performance is only one dimension of any solution. Java/Hibernate has the added advantage that it is much easier to move to TDD - eventually all your code will be under automated unit test, so that any future changes are easier and can be made with more confidence.

Java also creates the opportunity to create a Domain Model, if the business domain that the batch is working on is particularly complex.

Code written against domain model objects tends to express the business process and rules directly rather than burying them deep inside of low level code. A Domain Model that is well matched with the business domain also tends to easier to adapt to changing business needs.

So even if Cobol performs (slightly) better there are still plenty of good reasons to go the Java/Hibernate route (provided the potential is exploited appropriately).
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic