Sets where session state data will be stored in a web application.
|Database ||The session state data will be stored in a SQL database.|
|In Process ||The session state will be stored in the memory of the web server process.|
|Redis ||The session state data will be stored in a Redis-based distributed cache.|
It is important to note that the choice of session state provider depends on the requirements and infrastructure of the application. For containerized deployments, it is recommended to use distributed solutions such as Redis to ensure the availability and persistence of session data. In addition, please note the following:
- Select the "In Process" value if your application runs on a single server and does not require high availability. Note that if the application is restarted or recycled, session data will be lost.
- If your application runs on multiple servers and requires high availability, it is recommended to select the "Redis" setting. Redis allows session data to be shared and synchronized between server instances, which improves scalability in distributed environments. In addition, Redis offers fast in-memory storage.
- Select the "Database" option if your application requires persistence and scalability. By using a database, more comprehensive storage options with advanced query capabilities are provided.
This property applies only at design time.
To apply the corresponding changes when the property value is configured, execute Build any object with the purpose of generating the *.config files.
This property is available since GeneXus 18 Upgrade 4.
HowTo: Configure Session State In ASP.NET Core