01-29-2010

Still need to figure out the HTTPS issue.  Now that I've got a handle on the Terracotta/Ehacache integration, I suppose I should go the full mile and add in Hibernate L2 caching into the mix.  Learned that you can hit the server to see what configuration it is using: http://localhost:9510/config .

Ok, how can I test Hibernate's L2 caching capabilities?  I'll need a dirt simple Hibernate app that talks to a remote db.  An in-memory db probably won't show the performance increase that is supposed to happen.

I was reading some notes on how using detached Hibernate sessions and Terracotta can greatly improve database performance because you only hit the database twice: once to read and once to write.  All intermediate state changes are in-memory only, which are distributed via Terracotta, which greatly improves performance.  The trick is to be able to have enough control over Hibernate so that you can store the detached object in a distributed cache and then re-attach it at the appropriate time.  If you are using Spring and letting it manage transactions for you, do we have that kind of control?