Help Needed - Hibernate Vs Stored Procedure

[Ranjitdani]

we planned to rewrite our System in Java, Which was previously running in Stored procedure.
More than 5 Applications calls the procedure which inserts and updates some set of records after the post transaction which has been done in the background.

Now we planned to take the stored procedure out and do a application in java with Hibernate. Will this can be done. with Hibernate? As the application should be running in the back ground and all the interdependend application should call the back ground application for transaction.

Waiting for a Reply

[rajatssekhar]

we planned to rewrite our System in Java, Which was previously running in Stored procedure.
More than 5 Applications calls the procedure which inserts and updates some set of records after the post transaction which has been done in the background.

Now we planned to take the stored procedure out and do a application in java with Hibernate. Will this can be done. with Hibernate? As the application should be running in the back ground and all the interdependend application should call the back ground application for transaction.

Waiting for a Reply

First, Why you are going for code based solution from stored procedure? Using code in this situation has some concerns.

Client/server data shuttling: When queries are made from Java code, potentially large amounts of data are shuttled back and forth between the application server and the database. This can greatly impact performance.

Transactions opened from outside the database: A transaction is often created for each query executed from the Java code within an application server. When a single logical operation requires multiple queries, many individual transactions may be created.

Tight coupling of database schema and Java code: The database structure is exposed to the Java layer. Hence, future changes to database structure may require changes to the Java code. As with Java class structure and member data, the database structure should be abstracted from other layers in the software.

Software release coordination: Because the Java code depends on the database structure, database releases that contain schema changes must be coordinated with releases of the dependant Java code. It's often difficult to coordinate such releases. Furthermore, if one system must be rolled-back due to a problem, dependant systems must be rolled back also.

If you are ok with above, then no issues in using Java here.

[Ranjitdani]

Thank you Sekhar .. Let me take this a look