You have successfully deployed your game in Edgegap. Great! The next step is to automate the deployment for your production traffic.
We support Open Match Project. You can find out more about this opens-source matchmaker here.
If you want to learn more about the call flow between Open Match and Arbtrium, click here.
Building a matchmaker is no simple task. There are a lot of components to handle, and what Open Match offers is a matchmaker's template that make the creation process easier. It handles all the complexity that tends to be the same for every matchmakers. By combining Open Match with Edgegap, the backend, infrastructure and automated scaling parts will be taken care of for you. This means you can concentrate of making the matchmaker do what it needs with these 3 Open Match components: Frontend (Bridge between client and matchmaker), the Match Function (Brain behind the decision) and the Director (Assignment to the game server). As you know, every game is different and can have its own way to authenticate a player, create a server, and match players based on skills or game scenarios. You will need to build these 3 components to fit your specific needs.
If you use this solution we recommend you to follow this tutorial. Keep in mind that everything in this tutorial is for learning and testing and is not production-ready. In a production environment, all the Kubernetes management would be done by Edgegap.