 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
| | | Shared cache best practices? | Shared cache best practices? 2004-01-08 - By Erik Beijnoff
Back
Thanks for the responses. You've been verry helpful. I've gotten some
alternative approaches to think of it, and those of you who have
answered seems to lean towards the Entity Beans approach.
> Depending on your container, you may get automatic invalidation for
free -
> by using the appropriate "commit option" (without needing JMS).
> This is all assuming that all modifications to the tables that have
the cached data are being done through entity beans.
> In any event, it seems entity beans would be a good fit. You will need
to decide whether to
> keep your strategy of separate caches per web server (which will mean
an app server local to each web server).
For the moment I am not using Entity Beans or EJB. Just a domain model
made out of Pojos manipulated through a DB Peer, so it's really not an
app server for each web server, rather several web server with caches.
If I where to use Entity Beans, do they make a good joob replicating
over several servers, or can I expect the app server holding the Entity
Beans to become a bottleneck in the future?
Best regards Erik Beijnoff
===========================================================================
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".
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:eXclaimer = "http://www.exclaimer.co.uk" xmlns:o =
"urn:schemas-microsoft-com:office:office"><HEAD><TITLE>Meddelande</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1276" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><SPAN class=722522316-07012004><FONT face="Lucida Sans Unicode"><FONT
size=2><SPAN class=646363008-08012004><FONT face=Arial>Thanks for the responses
.
You've been verry helpful. I've gotten some alternative approaches to think of
it, and those of you who have answered seems to lean towards the Entity Beans
approach.</FONT></SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=722522316-07012004><FONT face="Lucida Sans Unicode"><FONT
color=#0000ff><FONT size=2><SPAN class=646363008-08012004><FONT
face=Arial></FONT></SPAN></FONT></FONT></FONT></SPAN> </DIV>
<DIV><SPAN class=722522316-07012004><FONT face="Lucida Sans Unicode"><FONT
color=#0000ff><FONT size=2><SPAN class=646363008-08012004><FONT
face=Arial>> </FONT></SPAN>Depending on your container, you may get
automatic invalidation for free - <SPAN class=646363008-08012004><FONT
face=Arial> </FONT></SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=722522316-07012004><FONT face="Lucida Sans Unicode"><FONT>
<FONT
color=#0000ff><FONT size=2><SPAN class=646363008-08012004><FONT
face=Arial>></FONT> </SPAN>by using the appropriate "commit option"
(without needing JMS). <SPAN class=646363008-08012004><FONT
face=Arial> </FONT></SPAN></FONT></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=722522316-07012004><FONT
face="Lucida Sans Unicode"><FONT><FONT><FONT color=#0000ff><FONT size=2><SPAN
class=646363008-08012004><FONT face=Arial>></FONT> </SPAN>This is all
assuming that all modifications to the tables that have the cached data are
being done through entity beans.<SPAN class=646363008-08012004><FONT
face=Arial> </FONT></SPAN></FONT></FONT></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=722522316-07012004><FONT
face="Lucida Sans Unicode"><FONT><FONT><FONT color=#0000ff><FONT size=2><SPAN
class=646363008-08012004><SPAN class=722522316-07012004><FONT
face="Lucida Sans Unicode" color=#0000ff size=2>> In any event, it seems
entity beans would be a good fit. You will need to decide whether to
</FONT></SPAN></SPAN></FONT></FONT></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=722522316-07012004><FONT
face="Lucida Sans Unicode"><FONT><FONT><FONT color=#0000ff><FONT size=2><SPAN
class=646363008-08012004><SPAN class=722522316-07012004><FONT
face="Lucida Sans Unicode" color=#0000ff size=2>> keep your strategy of
separate caches per web server (which will mean an app server local to each web
server).</FONT></SPAN></SPAN></FONT></FONT></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=722522316-07012004><FONT
face="Lucida Sans Unicode"><FONT><FONT><FONT color=#0000ff><FONT size=2><SPAN
class=646363008-08012004></SPAN></FONT></FONT></FONT></FONT></FONT></SPAN> 
;</DIV>
<DIV><SPAN class=722522316-07012004><FONT
face="Lucida Sans Unicode"><FONT><FONT><FONT size=2><SPAN
class=646363008-08012004><FONT face=Arial>For the moment I am not using Entity
Beans or EJB. Just a domain model made out of Pojos manipulated
through a DB Peer, so it's really not an app server for each web server, rather
several web server with caches. If I where to use Entity Beans, do they
make a good joob replicating over several servers, or can I expect the app
server holding the Entity Beans to become a bottleneck in the
future?</FONT></SPAN></FONT></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=722522316-07012004><FONT
face="Lucida Sans Unicode"><FONT><FONT><FONT face=Arial size=2><SPAN
class=646363008-08012004></SPAN></FONT></FONT></FONT></FONT></SPAN> </DIV>
<DIV><SPAN class=722522316-07012004><FONT
face="Lucida Sans Unicode"><FONT><FONT><FONT face=Arial size=2><SPAN
class=646363008-08012004>Best regards Erik
Beijnoff</SPAN></FONT></FONT></FONT></FONT></SPAN></DIV></BODY></HTML>
===========================================================================
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".
<p>
|
|
|
