You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To move the application to the cloud, HTTP sessions should not be stored locally on individual instances. I deployed EUSurvey in the cloud using the latest Helm pull request, and after terminating one pod, the login session was lost.
After reviewing the SessionService, I noticed that session management is handled through the request object, which means sessions are tied to the application server.
To avoid losing sessions during pod restarts or scaling, session data should be externalized to a persistent store, such as a database or a distributed cache like Redis. This would allow for more transparent session management and ensure seamless failover and scaling in a cloud environment.
The text was updated successfully, but these errors were encountered:
To move the application to the cloud, HTTP sessions should not be stored locally on individual instances. I deployed EUSurvey in the cloud using the latest Helm pull request, and after terminating one pod, the login session was lost.
After reviewing the SessionService, I noticed that session management is handled through the request object, which means sessions are tied to the application server.
To avoid losing sessions during pod restarts or scaling, session data should be externalized to a persistent store, such as a database or a distributed cache like Redis. This would allow for more transparent session management and ensure seamless failover and scaling in a cloud environment.
The text was updated successfully, but these errors were encountered: