On Tue, Jan 3, 2012 at 11:50 AM, Scott Battaglia <scott.battag...@gmail.com> wrote: > On Tue, Jan 3, 2012 at 11:36 AM, Marvin Addison <marvin.addi...@gmail.com> > wrote: >> >> > Registries generally don't need the durability that comes with RDBMS, >> > and unless you are already outfitted with clustered RDBMS tech and the >> > resources to management it, the complexity is likely not worth the >> > trouble. >> >> I've really warmed up to that view. The use of "Remember Me" might be >> a counter argument, but as I said we don't use it and don't plan to in >> the foreseeable future. > > > The amount of durability needed is specific to an institution, which is why > we support multiple ticket registries. > > Changes have been made in the cas4-api branch to make ALL registries perform > better with less issues (that includes all of the ones that use > serialization such as Ehcache).
Are any of those changes candidates for 3.x? Bill > > Cheers, > Scott > > >> >> >> > given the proliferation of hardware virtualization and the >> > redundancy and vertical scaling they often provide, my default >> > recommendation is a single node CAS deployment with in-memory Ticket >> > Registry and active/passive configuration for disaster recovery. >> >> The point about virtualization pretty much invalidates the argument >> about active-active setups making more efficient use of resources. >> (The consideration of the cost of system administration/patching on >> hosts that are unused 99.9% of the time may yet be fair.) >> >> > For situations that insist on a multi-node CAS deployment, my default >> > would be to go with a distributed in-memory Ticket Registry like >> > Ehcahce. >> >> The use of Terracotta underneath a distributed Ehcache instance is the >> showstopper for me. It smelled of magic and mystery in my brief >> experience with it, which are smells I associate with headaches in >> production. >> >> I'm heavily leaning toward memcached. (Sans repcache if it matters.) >> >> M >> >> -- >> You are currently subscribed to cas-dev@lists.jasig.org as: >> scott.battag...@gmail.com >> >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: wgt...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@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-dev
