Require Your suggestions on Portable Database interfacing tech.

Dear All,

My name is Arpan Bansal and I am working as a Manager in Newgen Software Technology.

We have a Document Management Product that is built using J2EE Technology on Server side. To give you an overview:

1. It's repository part is available on MS SQL/Oracle and built as set of Tables and Stored Procedures.

2. We have a middle layer written as TCP/IP based Java/JDBC Server alternatively as EJBs ( stateless Session Beans with JDBC), which interfaces with RDBMS and provide XML API for applications.

As I mentioned our repository is built using Stored Procedure. This has made porting in terms of supporting new database server say DB2 an issue for us.

We want to go away from SPs and sees following as options.

1. Porting SP logic to JDBC. But JDBC it self is not 100% portable?

Any suggestions on this

2. Using any middleware like hibernet or POJO?

Any recommendations? Will it be a right approach? Will performance be an issue?

3. Will any thing else like any specific design pattern ( with JDBC ) can help us.

Your help is highly appreciated.

Thanx in advance

Best Regards

Arpan

[1187 byte] By [Arpan_Bansala] at [2007-10-2 13:07:26]
# 1

Hello,

I would suggest looking into Hibernate. With tools provided by Hibernate framework it's easy to import existing schema and build DAO layer without too much effort. If you application is not mission-critical (no real time performance issues), then Hibernate would bring a lot to your table. On the other hand, caching and improper use of cascading/object mapping might give you a real headache if your app needs those real-time capabilities. Still, for bulk data handling Hibernate works well.

If you're looking to go away from stored procedures you could implement your logic in Java and use Hibernate for persistence.

HTH,

Mark

markcitizena at 2007-7-13 10:32:33 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...
# 2

Thanx Mark, Thanx alo't

1. Performance of the application is critical.

2. It is a product and 300 - 400 concurrent users/requests with response time under 2sec. is basic requirement.

3. By design it is very scalable right now. Any thing, which limits performance or capability to handle concurrent request, may not be acceptable.

4. Do you still recommend Hibernate?

5. Or if we go for DAO pattern with our persistence logic(JDBC) that will be better. Will it give reasonable portability?

Best Regards

Arpan

Arpan_Bansala at 2007-7-13 10:32:33 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...