We use CAS 5.2.x with Oracle via JDBC query/attributes. Sounds very similar :)
In my case, I went with a 3-node redis/sentinel cluster for my ticket registry, as I am the only one maintaining this deployment and I'm completely unfamiliar with hazelcast. Redis, with sentinel and an *odd number* of nodes, is a solid HA-capable solution. I build a war that I run in a jetty docker container, personally. Embedding the server application just seems icky to me. This tightly couples that with the build artifact of CAS, which means you couldn't touch one without touching the other. -- - 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/6519df53-f26a-45ae-8820-03885fda06ab%40apereo.org.
