On Sun, Mar 24, 2013 at 8:28 AM, jleleu <[email protected]> wrote: > Hi, > > At my company (SFR), we have millions of hits every day. > > 1. We don't have any session replication between Tomcats, but a session > affinity : you get the login page from Tomcat 1, authenticate at Tomcat 1... > Web sessions are only required for login process whereas tickets are stored > in the registry.
This is how Unicon has deploy every multi-node CAS deployment that I'm aware of. Keep it simple. Load balancer session affinity for login-flow. Ehcache for shared ticket registry. > 2. We tried using DB but got many issues with deadlocks, and finally gave up > on DB. I would definitely not recommend using DB, but that's just my point of > view. Ehcache is great : simple but very resources consumer, we now use > Memcached which is very effective and simple (it's out of the box since a > long time but highly improved since 3.5.0 by using Kryo for serialization) > 3. Using Memcached, you would not have to worry about cleaning tickets ;-) Same with Ehcache of course. Ehcache is simpler in that you only need to a few extra config files and there's nothing else to learn, deploy or maintain. Memcached may scale better and if you are supporting millions of users, is likely worth the modest increase in deployment complexity. Best, Bill > > Hope it helps. > Best regards, > Jérôme > > -- > 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 -- 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
