You do realize you will have to configure and tune any solution :-) Before comparing solutions, I would recommend defining your requirements and your tolerance for failure (if you have not). For example, Is it acceptable that if a node (that has > 99.9% uptime) goes down, a user must re-authenticate? Is that extra .1 worth whatever the cost? I can't answer that for you. What are your SLAs? (I don't know if anyone has done an EhCache vs. Memcache load test?)
On Wed, Aug 7, 2013 at 2:15 PM, Paul B. Henson <[email protected]> wrote: > 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/<http://www.csupomona.edu/~henson/> > Operating Systems and Network Analyst | [email protected] > California State Polytechnic University | Pomona CA 91768 > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/**display/JSG/cas-user<http://www.ja-sig.org/wiki/display/JSG/cas-user> > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
