Caching Scenarios. Caching is a quick and easy way to save roundtrips between your application and where you store your data. However, it’s not as easy as just snapping a map into your application – to really leverage a cache, you not only have to understand where a cache can be used, but how it can affect what your application does and how your architecture is used. Definition of caching Caching is the use of an intermediate and temporary data store to preserve computation or data retrieval time. It sounds simple, but it's worth taking the time to consider cache strategies and approaches. (What’s more, if you’re really going to leverage the technology and tools, it’s worth wondering if you can get rid of the ‘intermediate’ and ‘temporary’ label there.) Definitions Some definitions are in order to make discussion easier. Data. Data can have a lifetime, after which the data is considered stale and inappropriate for use. Cache. Datasource. Participant.
Writethrough/Readthrough. System of Record. Transaction.
Open Source Cache Solutions in Java - Open Terracotta. Open Source Cache Solutions in Java - OSCache. OSCache is a widely used, high performance J2EE caching framework. In addition to it's servlet-specific features, OSCache can be used as a generic caching solution for any Java application. A few of its generic features include: * Caching of Arbitrary Objects - You are not restricted to caching portions of JSP pages or HTTP requests. Any Java object can be cached. . * Comprehensive API - The OSCache API gives you full programmatic control over all of OSCache's features. Open Source Cache Solutions in Java - SwarmCache. Open Source Cache Solutions in Java - JBoss Cache. Jboss.org: community driven. SwarmCache - Cluster-aware Caching for Java.
Home.