It's comparing apples and oranges ;-) ... iBATIS in the end also boils down to JDBC calls, so you can assume it's a bit slower than JDBC (the price for more flexibility and ease of use). But with iBATIS you end up with java objects while with JDBC you end up with primitives/string that you you still have to put into your object model.

With iBATIS you also do get stuff like lazy loading, caching, ... already built in, which you have to develop for JDBC.

Regards,
Sven

P.S. look in the mail archives on "performance", there have been some rants on performance in the past.


Tony Qian wrote:

All,

I'm wondering if anybody has some stats on iBATIS' performance agains direct JDBC calls.

Thx,
Tony

Reply via email to