Thanks Chris for elaborate response to my query. I really appreciate your taking time out for this. Let me correct my self when I said EJB vs Hibernate. I actualy ment EJB Entity Beans vs Hibernate. Sorry for the confusion caused. As far as my analysis over there is concerned I read in one of the articles (http://www.roseindia.net/hibernate/hibernate_architecture.shtml
) that Hibernate comes with its own Connection Pooling module and transaction Manager module which does not have the desired performance. Your assumption of 50 TPS holds true for our application. What I did not know was that this figure does not qualify as high TPS. That would certainly change things a bit. I was not aware of the IBatis project and would certainly have a look there. Just to summarize from the discussion, my concerns were mainly about a) connection pooling - for which you have advised to make use of the App server,(instead of hibernate connection pooling module or any other) b) transaction - which in this case can be managed by JDBC itself and c) performance - which again is not a major factor with the given TPS value. Once again thanks for the insight.