JDBC performance is inefficient ????


Could anybody argues about the following statment

"JDBC performance is inefficient  "

If  you agree, say why
If you don't, tell me why please

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

nawafAuthor Commented:
Edited text of question.
nawafAuthor Commented:
Edited text of question.

According to Microsoft :-

Visit this URL:


Best tof luck.
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

It depends on how you view inefficient.

My answer is it is efficeint.

Here are my views:

1. If your using JDBC-ODBC bridge, you have to realize that there will be an overhead in the processing time compared to a direct connection.
2. As we all know, Java is quite slow in terms of processing, but they have come up with HotSpot runtime optimizer to optimize the processing.
3. It depends on how you have coded it, if per transaction you use a new connection, of course there will be lots of overhead in performing the connection to the database. You can do the transaction with connection pooling to lessen the connection overhead.
4. In terms of maintenance, it will be efficient because it is maintainable, only few code or even none have to be modify to migrate to another database (if you have an initialization file for customization)

Hope this satisfy your question.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial

this is supposed to be a discussion, no need to lock the question.

my answer is:
What is 'inefficient' ?

btw. JDBC is standard (for database interface) - not implementation.
some specific (JDBC driver) implementations may be good, some not.
nawafAuthor Commented:
inefficient in terms of

 Complex data type (images, sounds,etc..)

 speed when used with applets

 Coul it be better ? How ?

nawafAuthor Commented:

"JDBC is a very limited interface that is targeted primarily at transferring data from an SQL database to a Java client"

my answer (again)

JDBC is standard for database access - not implementation.

so we CAN'T talk about performance and speed at all.  
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.