Subject: Persistence with JDBC ??? 2005-10-10 - By Juan Carlos
Back
Hi everybody, I'm migrating a legacy system from pl/sql to J2EE.
Initially i had to use an implementation of JDO, but after trying to
translate lots of query without getting a good performance and, in many
cases, being almost impossible to translate them, we are planning to use
other persistence system. Some people suggested me to use JDBC and call
directly stored functions or execute statements.
I've tried it and it performs much faster than with JDO. I think it's
normal, since now we are avoiding to create the objects and simplifying
considerably the number of queries (JDO generates lots).
Although JDBC is faster, I know that there are some issues I should
consider before adopting it. The one that more worries me is the cache
management. The system manages lots of data and users, and same queries
are invoked once and other.
Do you think that JDBC is a good solution? Is that enough for a big
web-based system?
I know that I could use Hibernate but initially the chiefs didn't want
to use free software for persistence, since is a very critical system
and they always want to have some comercial ''support''..
Another thing is that the system is based only in servlets (with Struts)
and doesn't use any kind of EJB.
Thanks in advance!!
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
