blob: f5d1a2c92fccac27182ae5f03ce5bc5d43d56b9b [file] [log] [blame]
<?xml version="1.0"?>
<title>Java Caching System</title>
<author email="">Pete Kazmier</author>
<author email="">Aaron Smuts</author>
<section name="Java Caching System">
JCS is a distributed caching system written in java for
server-side java applications. It is intended to speed up
dynamic web applications by providing a means to manage cached
data of various dynamic natures. Like any caching system, the
JCS is most useful for high read, low put applications. Dynamic
content and reporting systems can benefit most. However, any
site that repeatedly constructs pages, dropdowns, or common
search results form a database that is updated at intervals
(rather than across categories continuously) can improve
performance and scalability by implementing caching. Latency
times drop sharply and bottlenecks move away from the database
in an effectively cached system.
The JCS goes beyond simply caching objects in memory. It
provides several important features, necessary for any
Enterprise level caching system:
<li>Memory management</li>
<li>Disk overflow (and defragmentation)</li>
<li>Element grouping</li>
<li>Quick nested categorical removal</li>
<li>Data expiration</li>
<li>Extensible framework</li>
<li>Fully configurable runtime parameters</li>
<li>Remote synchronization</li>
<li>Remote store recovery</li>
<li>Non-blocking "zombie" (balking facade) pattern</li>
<li>Optional lateral distribution of elements via HTTP, TCP, or
<li>Remote server chaining (or clustering) and failover</li>
These features provide a framework with no point of failure,
allowing for full session failover including session data across
multiple servers.