Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

In distributed architecture (typical three tier consisting of thin client, middleware & database) which type of JDBC driver should be used and why?

April 26, 2017Architecture client consisting database distributed JDBC middleware Tier type

0

Posted

In distributed architecture (typical three tier consisting of thin client, middleware & database) which type of JDBC driver should be used and why?

1 Answer

0

Posted

Location: http://www.jguru.com/faq/view.jsp?EID=21804 Created: Mar 8, 2000 Modified: 2000-03-23 12:17:42.054 Author: Zahid Shaikh (http://www.jguru.com/guru/viewbio.jsp?EID=21793) Question originally posed by sat d (http://www.jguru.com/guru/viewbio.jsp?EID=14705 Normally in 3-tier architectures, you would preferably connect to database via middleware. Pure java drivers are slower than native driver but they do not require any client-side installation. So for middleware, as perfomance is important, native JDBC drivers like Oracle’s OCI driver should be preferred. Also native installation(like ODBC or Oracle’s Sqlnet ) would be required at middleware level but it would not affect the clients. In the exceptional case, if the database is needed to be accessed by thin client than pure Java driver like Oracle’s thin driver is recommended as they do not require any client-side installation.