JavaWorld
addict
Reged: 06/20/03
Posts: 482
|
|
An ounce of prevention: Avoid J2EE data layer bottlenecks
|
Anonymous
Unregistered
|
|
A very good article introducing an J2EE issue indeed worth serious consideration. I hope it gets the feedback it deserves.
Rgds, Kris
|
Samb
Unregistered
|
|
Provides good peek into the issues
|
Cameron
Unregistered
|
|
For coherent clustered caching in J2EE, see Tangosol Coherence: http://www.tangosol.com/coherence.jsp
|
Anonymous
Unregistered
|
|
I wish Coherence worked with CMP 2.0. 
|
Anonymous
Unregistered
|
|
It seems that this article assumes entity beans will be the data API of choice. Am I right in reading this into the article? If so, what about other API options, such as JDO, Hibernate and Castor? Does their performance put them outside of enterprise scope?
|
Anonymous
Unregistered
|
|
I wish Coherence was free, but its a great product and Cameron wouldn't do well without getting paid. That said there are alternatives (not as powerful as Coherence) that are both free and CMP 2.0 compliant.
|
ckeene
stranger
Reged: 04/07/04
Posts: 4
|
|
In the article, I was not assuming the use of Entity Beans.
In many cases, it makes sense to use plain old java objects for data access even in a J2EE application because it eliminates the overhead of Entity Beans (e.g., remote access etc). This is particularly true if you are using a "best of breed" object persistence layer like Oracle Toplink or Persistence EdgeXtend.
The basic premise of the article is that the "stateless server" model which separates data access from data caching has built-in performance limitations. The J2EE vendors themselves have addressed some of these problems with their CMP caching (but there are some significant gotchas - maybe the subject for a future article 
For an example of an integrated data access and caching layer that supports J2EE entity beans as well as Plain Ol' Java Objects go to <insert shameless plug here>:
http://www.persistence.com/download/download.php
- chris
|
Anonymous
Unregistered
|
|
Sorry, but that article is pure advertising for your product.
In my opinion, the entity beans concept will never
work because O/R mapping in general does not work apart
from small or trivial cases.
The numerous different commercial and open source approaches prove that. Your product tries to fix the problem boosting
the application server with lot's of things, the
database normally does. This makes trouble shooting
and tuning extremely complicated since you inroduce
yet another layer increasing the total complexity degree.
Remember: With a rocket, you can even make
a toilet door fly,
but is it worth the proove?
|
ckeene
stranger
Reged: 04/07/04
Posts: 4
|
|
You are right - Entity Beans lost a long time ago.
Most of your other comments seem somewhat misplaced - you might try reading the article before you critique it. 
- chris
|
ckeene
stranger
Reged: 04/07/04
Posts: 4
|
|
Here are some additional places to go for further information:
1. Persistence object-relational mapping
2. Persistence distributed object caching
Hope that helps
- chris
|
Maneye
Unregistered
|
|
Hi, i would like to know about 'That said there are alternatives (not as powerful as Coherence) that are both free and CMP 2.0 compliant.' Your reply will be much helpful for my college work
|
Anonymous
Unregistered
|
|
The problems you talk about are not limited to J2EE!? Why did you target J2EE as having these problems...anyone who is building a web application along the lines of ordering on the scale of Amazon is going to face the same problems!
|
Previous
Index
Next
Threaded
Edit
Reply
Quote
