 | 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-07 - By Erik Beijnoff
Back
Im facing a situation where my web server holds a rather extensive cache that
is retrieved from a database. I'm seeking a way to be able to connect as many
web servers as I'd like to that database and let each server be notified of the
updates to the database so that they can keep their caches up to date. I'm
looking for best practices in this area.
I'm aware of that one of the possibilities would be to put the cache on a
common machine that all web servers access. However, this is not quite the
solution I am looking for. The cache does not need to be same for all servers.
On the contrary actually. The system is structured in such a fashion that each
web server only holds in it's cache the information that is requested on that
particular server for the moment. This could mean that each web server has
completely different things in their caches. What I'm looking for is a
signaling system that tells all web servers that are using that particular
database that the data has changed in the database so that they can invalidate
that particular portion of their caches so that it can be reread at the next
request.
I suppose that keeping a separate cache server going also would create a
somewhat rather large amount of overhead, granted, it would though be easier to
gurantee consistency.
One of the options that I'm pondering would be a registration and
deregistration process in a table in the database whenever a new web server
connects to the it, and then let the servers signal updates to all the others
through http or RMI or some other suitable method.
Or is this one of those magic moments where EJB actually would make sense?
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><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859 (See http://iso-8859.ora-code.com)-1">
<META content="MSHTML 6.00.2800.1276" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2><SPAN class=530151715-07012004>Im facing a
situation where my web server holds a rather extensive cache that is retrieved
from a database. I'm seeking a way to be able to connect as many web servers as
I'd like to that database and let each server be notified of the updates to the
database so that they can keep their caches up to date. I'm looking for best
practices in this area.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=530151715-07012004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=530151715-07012004>I'm aware of that
one of the possibilities would be to put the cache on a common machine that all
web servers access. However, this is not quite the solution I am looking
for. The cache does not need to be same for all servers. On the contrary
actually. The system is structured in such a fashion that each web server only
holds in it's cache the information that is requested on that particular server
for the moment. This could mean that each web server has completely different
things in their caches. What I'm looking for is a signaling system that tells
all web servers that are using that particular database that the data has
changed in the database so that they can invalidate that particular portion of
their caches so that it can be reread at the next request.
</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=530151715-07012004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=530151715-07012004>I suppose that
keeping a separate cache server going also would create a somewhat rather large
amount of overhead, granted, it would though be easier to gurantee
consistency.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=530151715-07012004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=530151715-07012004>One of the options
that I'm pondering would be a registration and deregistration process in a
table
in the database whenever a new web server connects to the it, and then let the
servers signal updates to all the others through http or RMI or some other
suitable method.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=530151715-07012004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=530151715-07012004>Or is this one of
those magic moments where EJB actually would make sense?</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=530151715-07012004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=530151715-07012004>Regards Erik
Beijnoff</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </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>
|
|
|
