We use hazelcast. It comes up with cas so no external infrastructure. Not sure if other storage systems operate the same way.
Ray On Wed, 2022-03-16 at 09:09 +0100, [email protected] wrote: Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information. Hi, Can someone recommend me the "simplest" ticket registry which could be used to setup a highly available CAS infrastructure ? As we are not using any kind of distributed key/value database or cache architecture, there is no existing infrastrucure I could capitalise on and I am totally product agnostic. By simple I mean not requiring plenty of nodes to be resilient (Redis seem to have that kind of requirements) or high-level engineering and time consuming management. >From what I have read, Ignite looks nice but maybe it's just a feeling. Regards ________________________________ FreeMail powered by mail.fr<https://mail.fr> -- Ray Bon Programmer Analyst Development Services, University Systems 2507218831 | CLE 019 | [email protected]<mailto:[email protected]> I acknowledge and respect the lək̓ʷəŋən peoples on whose traditional territory the university stands, and the Songhees, Esquimalt and WSÁNEĆ peoples whose historical relationships with the land continue to this day. -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/3bb2695feb19af9983f5fe32f103ab2e425c16d0.camel%40uvic.ca.
