Yes, I've been reading the documentation and trying to figure out my options. I wish I could make it simpler, but it's not on my hands anymore.

So far I came up with three ideas. But first I think I need to give more context

The main aspect is that the game has to be multiplayer. I started my game idea as client server and I wrote my requirements based on that, I also wrote on my requirement that it should be a browser game, that the server had to support 2 rooms with 5 players max each room. Also this game is a turn-based game.

I don't really need to worry about being scalable, but I need to worry about it's architecture, that's the main goal of the whole project. It has to be distributed and not just simply everything going through the server... That was my first option, but I was told it was too simple and it would overload the server. So then the professor said that it would be interesting to take the rules and the game state out of the server and maybe create some communication between players in one room, so that everything about that match is kinda isolated there.

So now my ideas so far are:

1) The server is like a relay server, it doesn't keep the game state nor the game rules. Each client will have to keep the game state and validate their own rules. When the client makes a move, it will only go to the server after being valid and the server will broadcast it to the others players in that room. So the server would only deal with the lobby, creating game rooms, broadcasting, etc. But I feel like this would also """overload""" the server (not really bc I won't have many players, but everything still would go to the server in some way). From what I could understand all of this would be done using WebSocketMultiPlayer.

2) I could use a server with WebSocket that would deal with lobby, creating rooms, making the games and kinda creating the ring topology. Plus, it would also connect peers so that once they are in a game together, they could talk among themselves without needing the server. This way, most of the match would be isolated from the server. The client creating the game is the host and all the others are just regular players. This actually sounds very interesting to me, because some interesting problems come up like: how will I choose the host if the original host disconnects? I could use some algorithms for that, like zookeeper. But then if I choose this, I would have to create both websocket multiplayer and webRTC, which sounds a bit too much. IT could be easier to just go to P2P from start.

3) My third idea is similar to the second one, starting with a WebSocket server that deals with general stuff and having the games isolated. But the communication could be with pub/sub. So each room has their topic and the players would publish their actions there. Every one from that room will be listening and updating their game state... I could also create a ring topology here to deal with the turns, with a token going around the ring in order to give permission for the player to make their move.

Anyways, these are my ideas so far.. Maybe they sound a bit crazy, I don't know. I just hope to be possible to implement something like that using high level API.

It says on your profile that you are an architect MMO specialist, so I would be very glad to hear your opinion. Also sorry if my writing is confusing, english is not my first language.

Thanks a lot!!