This is my first blog about this topic, and I will follow with future posts to detail the different parts of highscores (scores) and the technologies and components involved.
You can also take a look at other existing information:
- PLAY THE GAME
- basic overview of the game (3mins)
- simplified high-level architecture
- source code on github
The motivation for the highscores (scores)
If you play a game, you usually want to compare yourself with others. To do this, you simply have to save scoring information somewhere and provide access for the players who want to see the highscores, even if they do not play the game.
The high-level architecture overview on scores
The objective was to implement this on the cloud with state-of-the-art runtimes, services, security topics, to cover microservices, and to have an easy scalable cloud architecture.
I developed the scores part and the functions-api for users.
The Game, Scores Service UI and the Highscores webapp are hosted on different runtimes and for the execution they will be loaded into a browser.