Cache

While working on a new JEE based project at the customer premise, I had to design and implement one of the most important parts of a product architecture – cache. Cache is defined as “a component that improves performance by transparently storing data such that future requests for that data can be served faster.” [Wikipedia]. There are several kinds of cache, and when you think of it, caching can be integrated in different layers of a product with different kind of cache: web browser cache, web Proxy cache, business-logic (applicative) cache, data access cache, DB cache etc. In this series I'll explore three different kinds of cache, which I integrated into this new product: web proxy cache, business cache, and data access cache. In this first part I'll concentrate on the web proxy cache.

 

yanai 13/07/2010 - 12:59

A customer I work for is in need for a distributed transactional cache.

Hibernate+EHCache is not an option since Hibernate is not the only persistence framework we use. we also have Spring JDBCTemplate and pure JDBC.

 

what we need is an easily distributed cache, with a transaction support. meaning the distributed cache is updated on transaction commit, or returns to its pre-transaction state on transaction rollback.

so far i didnt find anything usefull, any ideas?

avi 28/11/2010 - 09:56
Syndicate content