My naive view as someone standing on the sidelines and watching game companies, this sounds a bit odd. > Matchmaking is a complicated process, and when large p

My naive view as someone standing on the sidelines and watching game companies, this sounds a bit odd. > Matchmaking is a complicated process, and when large player populations are involved, many popular matchmaking approaches touch on significant areas of computer science including graph theory and massively concurrent processing My impression is that a good matchmaking algorithm (especially in ranked ladder play) can make or break a game - so when you finally shipped your game, it's awesome - then the balancing comes. After the balancing... matchmaking can still ruin it, so it seems to be a very delicate process. To cut it short, not the thing you'd want to grab some random code from github (from Google especially, where you never know how long it will be supported... ah well, at least better than Facebook) - we're not talking "I'm taking a webserver battle tested by millions of users" code reuse. So either it's a new problem for you, then you don't need scale. Or you have problems scaling - then you probably already have some matchmaking algorithm you're happy with - so where does this thing come in? Applying some engineering framework approach in making your thing scale? Sounds like a very small niche. Honestly a little confused.