Shared cache best practices? 2004-01-09 - By Erik Beijnoff
Back
You may be right. The only reason that I'm pondering other solutions
right now is that the system does not use Entity Beans for the moment.
But you definitely raise some vaild points. If I can avoid extra
maintenance problems it's of course worth some rebuilding.
-- --Ursprungligt meddelande-- --
Fr�n: A mailing list for Java(tm) 2 Platform, Enterprise Edition
[mailto:J2EE-INTEREST@(protected)] F�r Jeff Jensen
Skickat: den 9 januari 2004 16:41
Till: J2EE-INTEREST@(protected)
�mne: Re: Shared cache best practices?
Not knowing your situation and special needs that dictate creation of a
custom data caching service, Devil's advocate here...
A performant application usually caches some data. There are a number
of benefits to using entity beans, including the data caching they do
for you, "for free".
Are you sure the caching done by the entity beans is not enough for your
situation?
What are the decision points that lead you to think the application
requires extra caching?
You could encounter plenty of development work to add your own caching
and problems from its use for little gain. Be sure the gain is worth
the extra layer's development, debugging, and maintenance!
==========================================================================To
unsubscribe, send email to listserv@(protected) and include in the body
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected) and include in the body of the message "help".
|
|
