Jesse Davis: Has JDBC Kept up with Enterprise Requirements?

Prior to a few days ago, when I thought about JDBC, I thought I was thinking about a problem that has been solved. Our latest java.net article, Has JDBC Kept up with Enterprise Requirements? by Jesse Davis, has eliminated that kind of thinking for me. It shouldn't be a surprise that, as technology advances, problems that were "solved" may eventually become new unsolved problems. But... with JDBC, I just thought the solution that had evolved into JDBC Type 4 was a kind of permanent, at least a rather enduring, solution for the problem of abstracting applications from the details of underlying databases. Well, yes, it's true that JDBC Type 4 performs that abstraction. The problem, however, is performance and frameworks. Today, we as developers often don't directly access JDBC settings, because we often work with frameworks that apply their own implementations of JDBC. So, when it comes to performance, we face a dilemma: live with the framework's implementation of JDBC (which may not be ideally tuned for the application we're developing), or make our own custom version of the framework (and have to copy in our changes every time a new version of the framework is released). Umm.. no good choice there! Here's how Jesse describes it: While superior to other JDBC driver architecture types, most Type 4 drivers come with glaring limitations that make them impractical for today's Java-based enterprise appl...

Date: February, 23 2010
Url: http://www.java.net/blog/editor/archive/2010/02/23/jesse-davis-has-jdbc-kept-enterprise-requirements

Others News