While Java databases have become essential for Web applications, developing
performance-oriented Java Database Connectivity (JDBC) applications can be
challenging. But by following tried-and-true approaches, it is possible to
develop and fine-tune JDBC applications to make them run faster, jump higher,
and make fewer trips to the database.
Below, we present practical guidelines for many of the common JDBC
applications.
Guideline 1:
Use Metadata With Care
The first guideline is to be careful about using metadata. Although it's
almost impossible to write JDBC applications without database metadata
methods, you can improve system performance by minimizing their use.
Cache Information to Limit Executions
To return all result-column information mandated by the JDBC specification, a
JDBC driver may have to perform multiple queries, joins, and subqueries in
order to return ... (more)
What's the best way to develop and fine-tune your WebSphere applications to
run faster, jump higher…and make fewer trips to the database?
When creating optimized WebSphere applications that access data on your DB2
database, what kinds of challenges do you face? Creating DB2-enabled
WebSphere apps involves the Java Database Connectivity (JDBC) API, which can
be a challenge in itself. This article will look at various DB2-enabled
applications and offer some guidelines to help your WebSphere applications
run more efficiently when they connect to a DB2 database.
Designing WebSphere A... (more)
Pooling is great - except it's not very tunable, it's hard to map end users
back to connections in the pool, and if a connection ever becomes invalid
inside the pool, expunging only that connection from the pool is nearly
impossible; JDBC 4.0 addresses all these drawbacks
As a member of every previous JDBC Expert Group, it sometimes seems as if the
specification process moves too slowly for the few features being added or it
seems as if the new feature list is good, but "not good enough." The JDBC 4.0
specification fits neither of these perceptions. The specification includes a
... (more)
It's been over three years since the JDBC Expert Group held its first meeting
to gather requirements, requests, and pipe dreams for the JDBC 4.0
specification. In that meeting, we discussed a wide variety of topics,
including performance enhancements, clarifications on the existing JDBC 3.0
specification, and Ease of Development features. Unbelievably, everything but
the kitchen sink ended up making it into the release. In this article, we'll
look at several key features that made the enhancement list for JDBC 4.0, and
we'll discuss why those features are important.
At the time ... (more)
There was no ticker tape parade to accompany the release of the JDBC 3.0
specification, but many will be pleasantly surprised at its list of
enhancements that include everything from performance-tuning options to
support for extended-level database features.
This article describes, in detail, the new features that are available in
JDBC 3.0 and explains why they are important.
The JDBC 3.0 specification was shipped as part of the J2SE 1.4 release early
in 2002. The key goals of the JDBC Expert Panel were to align with the most
important features of SQL99, combine all the previous ... (more)
As vice-president of product operations, John Goodson leads the product strategy, direction, and development efforts at DataDirect Technologies. For more than 10 years, he has worked closely with Sun and Microsoft on the development and evolution of database connectivity standards including J2EE, JDBC, .NET, ODBC, and ADO. His active memberships in various standards committees, including the JDBC Expert Group, have helped Goodson's team develop the most
Sue Poremba
Scott Sellers
Anthony Franco
Daniel Morris
Wayne Walls
Niki Acosta
Jereme Hancock
Oren Michels
Marvin Wheeler
Douglas Kim
