EJB Benchmark

"As developers of EJB applications, we are often faced with the question of what architecture or design to use. There is no shortage of proposed and touted architectures and designs out there. We can use fine grained entity beans, coarse grained entity beans, entity beans with a session bean front end, and even stateless session beans to access our data. Lacking any hard data on which we can base our decision, we are often forced to rely on claimed best practices and pure marketing hype." stated Mr. Zawadzki, President of Urbancode SDI.

This benchmark seeks to change that. The goal of this benchmark is to provide some objective basis for the hard design decisions every EJB development team has to make. This is not a benchmark of application servers. Urbancode does not test the performance of one application server versus any other app. server. The benchmark does test the performance of five EJB design idioms all running on the same application server and using the same database.

The benchmark seeks to answer questions such as:

- how should I design my EJBs to maximize performance when accessing a single instance of data at a time?

- how should I design my EJBs to maximize performance when accessing a collection of data instances at a time?

- how should I design my EJBs to maximize the performance under a load?

The results are compelling. "You may be surprised to find that a flawed architecture of your EJB application could lead to performance 120 times slower than that possible with an appropriate architecture." stated Mr. Zawadzki.

If you are having performance troubles with your J2EE app, then visit Urbancode's EJB Benchmark. EJB Benchmark data is available online, as a Web based test, and as open source code for your own use.

product submission by Company Rep

Latest category updates via our RSS feed