Session Stickiness

Description

Session Affinity

In production environments, it is recommended to configure more than one instance of the Organizer services to support immediate failover and scaling, see sizing documentation.

For the jwt-viewer, to ensure that user sessions remain consistent, the load balancer must be configured for session affinity (also known as sticky sessions), ensuring that requests from the same user are always routed to the same server instance. The exact configuration depends on your infrastructure. Often, an Ingress may be present and can be configured accordingly.

The other Organizer containers do not require sticky sessions, only the jwt-viewer.

Load-Balancing, Session Affinity, and Sticky Sessions

When scaling the viewer across multiple instances to handle high traffic, a load balancer is required to distribute requests among these instances. To ensure that user sessions remain consistent, the load balancer must be configured for session affinity (also known as sticky sessions), ensuring that requests from the same user are always routed to the same server instance.

Session affinity is crucial when dealing with session-dependent systems. Without sticky sessions, the jadice web toolkit would face significant issues, as each request would require a recovery process on each server. This would lead to redundant storage of the same document across all server caches, hindering performance.