This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I'm developing a web application for an intranet comprising 300 workstations. I have decided to use Java Derby database. Other stuff that I will be using: JSP, Servlets, JDBC, Tomcat and Linux. Could you please suggest me which driver I've to use - embedded OR network/client?
Only my web-app will be using the database. However, the web-app will be accessed simultaneously from almost all workstations present in the intranet. Maybe, in future, there is a possibility that the same web-app could also be accessed from the internet. In this scenario, what should be used - embedded/network?
Joined: Mar 22, 2005
The number of users of the web app doesn't matter - you'd still want to use a connection pool to manage that. It sounds as if the embedded driver would be a feasible option. It does have the advantage of not requiring a separate server process, and of all communication happening inside of the JVM, thus improving performance.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com