On 8/7/2013 7:08 AM, Jérôme LELEU wrote:
Memcached processes can crash but it never happens for us
It's not just a matter of unplanned downtime; we deploy updates and
patches and do other routine maintenance on a regular basis. With the
memcached ticket registry, if we intentionally pull out a server for
maintenance, cache data is lost. With ehcache, it is not.
At this point, my short comparison list is:
ehcache:
native java, no extra moving parts (+)
fully replicated cache (+)
potentially more bandwidth intensive (-)
memcached:
extra piece to install/configure (-)
lost data on failure (-)
potentially less bandwidth intensive (+)
Neither one has any built in security for replication, so they both will
require either ssh tunnels or point-to-point VPNs for the communications
layer.
Definitely interested in more bullet points either way :).
Thanks…
--
Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/
Operating Systems and Network Analyst | hen...@csupomona.edu
California State Polytechnic University | Pomona CA 91768
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
