Rust has some advantages that might be useful for us in regards of the implemention of a game server:

• Safety against Null pointers, race conditions and all sorts of low-level threats.
• Predictable runtime behavior (zero cost abstractions and no garbage collector).
• (Almost) total control over the hardware (memory layout, processor features).
• Seamless interoperability with other languages ( C interop and FFI)
• Incredible runtime speed (comparable with C/C++)
• Simple package management with cargo
• Support for Generics in form of traits

An example of a game server implementation you'll find here:
Game Server in 150 lines of Rust

What are your thoughts about this? Would you prefer also Rust for a re-implementation?

When running stack build in the repo I get the output:

Error: While constructing the build plan, the following exceptions were encountered:

In the dependencies for openage-masterserver-0.1.0.0:
    aeson-0.9.0.1 must match >=0.11 (latest applicable is 1.2.2.0)

Plan construction failed.

Here is a small update after talking to n_brain:

He was recommending us to take a look for the glicko-2 rating system. There is also a pdf-File with mathematical explanations. n_brain said it would be best in combination with a community-based fairness reward system. Sounds like a really good approach to me, not reinventing the wheel and still practicable for our purpose. I would like to help implementing it in the future.

EDIT:
It is also implemented by CS:GO, so the article (saved with waybackmachine) that @chocoladisco linked in his comment is a good read, too. For the actual implementation see the pdf in this comment.

EDIT2:
Also the thoughts of the Guild Wars devs are worth a read and also the pvp-matchmaking algortihm explanation from their wiki.

EDIT3:
The paper from MS about Trueskill(TM).

EDIT4:
TeamFortress2-Matchmaking algorithm explained. I really like that Competitive Mode approach. Will take some notes from that video and publish them in a gist (link will follow).

EDIT5:
A Bayesian Approximation Method for Online Ranking
https://web.archive.org/web/20210501042619/https://jmlr.csail.mit.edu/papers/volume12/weng11a/weng11a.pdf

Originally posted by @simonsan in #9 (comment)

As we now have Kevin-CI, we should use it for the masterserver to test the build, maybe even the execution.

Unless travis-ci improved significantly (i.e. build time and container control), we won't use it again.

Proposed roadmap for the features of the masterserver:

• dedicated servers register at the masterserver
  • later: "official" servers authenticate via gpg
• the masterserver provides the alive dedicated servers to the client so it can choose
• the dedicated server is chosen automatically and people are redirected to the server they're gonna play on (matchmaking)
• the result is transmitted back to the masterserver so it can adjust the player ranks and perform matchmaking the next time

The ncZone has their matchmaking open-sourced and Eru (the creator of the system, @teheru) would like to help us as well to implement a good matchmaking system.

The matchmaking code is in his repository under /zone:
https://github.com/teheru/nczone/tree/master/zone

For further questions and as soon as we are able to start working on this we should contact him/tag him here.