Version 6.x has been out of support since May 14, 2024, and this corresponding section of the documentation is no longer maintained. We strongly recommend you upgrade to the latest supported version of 7.x and read the latest version of this documentation.
IdentityServer itself is stateless and does not require server affinity - but there is data that needs to be shared between in multi-instance deployments.
This typically includes:
The way you store that data depends on your environment. In situations where configuration data rarely changes we recommend using the in-memory stores and code or configuration files. In highly dynamic environments (e.g. Saas) we recommend using a database or configuration service to load configuration dynamically.
For certain operations, IdentityServer needs a persistence store to keep state, this includes:
You can either use a traditional database for storing operational data, or use a cache with persistence features like Redis.
Duende IdentityServer includes storage implementations for above data using EntityFramework, and you can build your own. See the data stores section for more information.