Note, this page describes WS availability and grouper client
- If you provision to a highly available LDAP or AD and apps read from that it addresses HA
- Apps can use DNSSRV or HAProxy or DNS load balancing or whatever LDAP / AD load balancing
- The SQL database that Grouper uses can be clustered somehow
- Instituions have used Oracle RAC (active/active), dataguard (readonly), etc
- Multiple WS and UI app servers/web servers can be load balanced for HA and high loads
- The WS is stateless, any load balancing is fine
- The UI is stateful (only for CSRF guard), and needs sticky load balancing. If a node fails the user will need to start over on another node (unless sessions are clustered across app servers)
- The loader process can be run on multiple nodes to improve performance and for fault tolerance
- This is Grouper 2.3.0 and above only
- You can sync a readonly copy of the database (e.g. offsite) and have readonly WS app servers and web servers handling requests (can use client failover or DNS load balancing or something)