Re: Enterprise Java

Mike skrev den 03-05-2007 21:01:

The lead web developer wants to use persistent data connections to
databases. This web service would grab data from MS SQL, the System i, and
untold # of other databases for use on the main City website. So speed is
the key here.

In my experience you only need a full J2EE stack (jboss, websphere, etc)
if you really really need EJB's.

The scenario you outline here would most likely only require a web
container (tomcat, jetty) with a database connection pool which either
may be builtin or an open source library.

Note also that if you need a lot of database traffic the placement of
the web server gets important - you basically want the most busy
connection to be as fast as possible - this usually means running on the
database server along with an optimized driver. For oracle it may even
mean running in the java process inside the database.

Another trick to get more speed is to cache aggressively and
proactively, but this is "standard tricks" so you should be able to read
them in most performance java books.