There are very fast, robust middle-tier caching products out there. Why reinvent the wheel? Try Javlin from http://www.objectdesign.com/htm/javlin_prod.asp. -----Original Message----- Date: Mon, 30 Jul 2001 11:06:02 -0700 From: Gene Chuang <[EMAIL PROTECTED]> Subject: Re: DB in EJB: stateless/stateful sessions vs BMP Entity vs BMP E ntit y with Fat Key My Fat Key pattern was initially a BMP counter-response to CMP bulk-loading optimization provided by many vendors (BEA in specific). However, we here at Kiko have been slight disenchanted with EJBs in general; a majority of our architecture now consists of SSB hitting JDBC. But middle-tier data-caching is still a high-priority concern of ours! We here, Lawrence being the principal author, have come up with an abstract middle-layer, clusterable, data cache we call ClusteredExpiryCache. (I have hinted of this pattern in another thread I posted regarding JMS and thread-safety). This pattern's expiry method is similar to Dimitri's Seppuku pattern: http://dima.dhs.org/misc/ However, unlike Seppuku, which depends on WL's propietary ReadOnly entity EJBs, our ClusteredExpiryCache is EJB- and vendor- independent. Our new architecture is still undergoing refinement, as we just pushed it out to production on our site last week. In the near future Lawrence will most likely publish his baby on theserverside or this newsgroup, so stay tuned! Gene Chuang Kiko.com =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
