EUSurvey is an opensource surveying tool. It features different types of questions, free text fields as well as more complex elements like editable tables and gallery elements. Results can be displayed as histograms, percentages or in full details and can be exported to different formats. All submitted answers (or a sub-set) can be published automatically on a dedicated webpage within the application. It is freely available for any organisation or administration, public or private and can also be deployed as an open source version.
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.
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.