Comments on: J2EE Applications and Clusters http://blog.webscale.co.in/?p=23 Just another WordPress weblog Sun, 27 Jun 2010 15:52:43 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Sergio Stateri Jr http://blog.webscale.co.in/?p=23&cpage=1#comment-59 Sergio Stateri Jr Fri, 22 Aug 2008 16:35:02 +0000 http://pitfalls.wordpress.com/?p=23#comment-59 Hi Scot, How can you to make hibernate cache use Memcached ? Did you implement a Hibernate cache provider ? thanks in advance. Hi Scot,

How can you to make hibernate cache use Memcached ? Did you implement a Hibernate cache provider ?

thanks in advance.

]]> By: Scott http://blog.webscale.co.in/?p=23&cpage=1#comment-58 Scott Wed, 06 Aug 2008 06:41:53 +0000 http://pitfalls.wordpress.com/?p=23#comment-58 I found the same as Darryl regarding Hibernate and Ehcache. We used Memcached with Ehcache, and quickly had our Hibernate objects in a distributed cache. We've had this running in production for a few months now with no issues. We noticed a very nice performance increase as well. The short version of the story is, I love Memcached :) I found the same as Darryl regarding Hibernate and Ehcache. We used Memcached with Ehcache, and quickly had our Hibernate objects in a distributed cache. We’ve had this running in production for a few months now with no issues.

We noticed a very nice performance increase as well.

The short version of the story is, I love Memcached :)

]]> By: mrozewski.pl » Blog Archive » Java: Pit Falls in Java Development http://blog.webscale.co.in/?p=23&cpage=1#comment-57 mrozewski.pl » Blog Archive » Java: Pit Falls in Java Development Tue, 08 Jul 2008 23:24:50 +0000 http://pitfalls.wordpress.com/?p=23#comment-57 [...] Java. Podają też swoje propozycje rozwiązań. Mnie w szczególności zainteresował artykuł J2EE Aplications and Clusters. Właśnie z podobnymi problemami walczymy ostatnio w pracy. W pierwszej fazie aplikacja była [...] [...] Java. Podają też swoje propozycje rozwiązań. Mnie w szczególności zainteresował artykuł J2EE Aplications and Clusters. Właśnie z podobnymi problemami walczymy ostatnio w pracy. W pierwszej fazie aplikacja była [...]

]]> By: Darryl Stoflet http://blog.webscale.co.in/?p=23&cpage=1#comment-56 Darryl Stoflet Sun, 22 Jun 2008 05:20:05 +0000 http://pitfalls.wordpress.com/?p=23#comment-56 Interesting writeup. On the 'stickiness' issue; most LB support a 'least conn' algorithm that that will help to avoid skewing of the load (to some degree, tho its obviously far from perfect since its a brainless least conn, that is it does not differentiate between load types). I am curious though why you did not discuss session replication in more detail. Every meaningful appserver offers session replication which ameliorates two problems here, one the skewing due to session sticky, and two, a user does not lose their session if the app server they were on goes down. As far as caching goes, I assume from your example that you are primarily talking about caching DB data. Ehcache has a very nice distributed replicated syncing cache. Typically most DB acces is done via an ORM or JPA. Hibernate, my favorite ORM/JPA allows ehcache to be plugged in transparently, and enabling the distributes cache is transaparent at the code level. So I'd be interested in understanding why you stated that the usage of ehcache would require to much rework. Interesting writeup. On the ’stickiness’ issue; most LB support a ‘least conn’ algorithm that that will help to avoid skewing of the load (to some degree, tho its obviously far from perfect since its a brainless least conn, that is it does not differentiate between load types).

I am curious though why you did not discuss session replication in more detail. Every meaningful appserver offers session replication which ameliorates two problems here, one the skewing due to session sticky, and two, a user does not lose their session if the app server they were on goes down.

As far as caching goes, I assume from your example that you are primarily talking about caching DB data. Ehcache has a very nice distributed replicated syncing cache. Typically most DB acces is done via an ORM or JPA. Hibernate, my favorite ORM/JPA allows ehcache to be plugged in transparently, and enabling the distributes cache is transaparent at the code level. So I’d be interested in understanding why you stated that the usage of ehcache would require to much rework.

]]>