Hi, I want to congrats you on the amazing framework. I love every part of it!
We are in the process of deploying our authoritative game. I’ve read almost all the posts related to scaling and the benchmark. I also read this helpful post (Why CockroachDB not PostgreSQL - #4 by novabyte). We would like to have a minimal scalable high-availability solution at the start. Right now, the enterprise solution is out of our reach financially. However, we will switch once the game gains attractions.
Our current setup will be, 1x load balancer, 2x Nakama servers, and 2x CockroachDB servers. As I understand, Nakama’s real-time features are all server-dependent. fortunately, all our real-time features are within the group. As long as the users are connected to the same server for that specific group, they should be able to experience the full features of the game. We don’t care about the geolocation of our users. As long as, players from the same group can interact together.
So we would like a load balancer that keeps track of the currently active groups and routes users accordingly. My questions are,
- Is this a viable and practical solution? if so, do you have some technical recommendations on how to achieve that on the client, server, and load balancer?
- Is the auth session also stored in memory inside the server? If so, is there a way to share it within the Nakama cluster?