We're doing the second: sessions stored in a Redis cluster with sticky sessions. This topology is simple and it scales pretty easily until it doesn't anymore [couple thousand simultaneous users]. You'll need to judiciously use your debugger and unix tools to find bottlenecks, as they're often hidden deep within the stack and present themselves in non-obvious ways. Important caveat: See the discussion from earlier this week on the mailing list about session replication and user authentication with the redisson session manager.
On Sun, Feb 16, 2020 at 9:06 AM Jonathan Yom-Tov <jonathan.yom...@sysaid.com> wrote: > hi, > > What kind of configuration do people usually use when deploying on a public > cloud (e.g. AWS)? An auto-scaling cluster with session replication? A > auto-scaling cluster with all sessions stored in an external cache? > > Jon. > -- Jonathan | exabr...@gmail.com Pessimists, see a jar as half empty. Optimists, in contrast, see it as half full. Engineers, of course, understand the glass is twice as big as it needs to be.
