Strategy for multi instances server without loadbalancer affinity

[ouvreboite]

Pre-submission Checklist

• I have checked that this question would not be more appropriate as an issue in a specific repository
• I have searched existing discussions and documentation for answers

Question Category

• Protocol Specification
• SDK Usage
• Server Implementation
• General Implementation
• Documentation
• Other

Your Question

Currently, using multiple stateless HTTP server instances result in an error each time a client reach another instance (it provides an Mcp-Session-Id that is not known by the other instance).

Header-based affinity in the LBs is a possibility, but I think it will still generate errors each time you restart an instance and a client have to switch to a new one (so quite frequently depending on your continuous deployment strategy).

Looking at the code, the stateless servers rely on IDataProtectionProvider to store the session data. By default, this is a local storage.

❓ To implement a distributed stateless server, would using a distributed key storage provider be a good practice? For example using redis to store the session info.

[ouvreboite]

@halter73 what do you think about that?