Create Game Management service #37
Description
Every 5-10 seconds, game management publishes a message like game.syncClient which contains a timestamp of the exact time that the swapping commences. Clients will receive the event and emit another event called serviceSync that has the code editor state inside it.
- Keeps track of code editor states and the challengeId corresponding to the problem the code in the editor is attempting to solve
- Tells clients when to swap
- Facilitates real-time communication with each connected client to ensure the game runs in sync and on schedule
- Only responsible for the execution and clock synchronization of the game
- After the game has concluded and final editor states are in, sends a request to match making
- Publishes message of game ending to kick off the process of tallying the final results in the scoring service. Data given to scoring includes the match ID and the snapshot of all final editor states