Best strategy for a multiplayer realtime server?

HI Steban,

Unfortunately, there is no simple answer to your question. Assuming you already have the server implemented, the next thing you should do is evaluate how much actual traffic it would be able to sustain. I’d recommend setting up a midrange droplet (like the 2GB of memory and 2 processors we have), getting the server running there and starting to run usage tests.

One of the best ways to verify how your server is behaving is using the top tool (you can read more about it here - http://blog.monitor.us/2012/04/key-linux-performance-metrics/ ), watch for the java process that your server will be running. Get some people to play the game (you will want to control how many people are actually there playing in this phase) and check how that affects server load. If the machine is seeing too much work (the load average by top is too high) you need a bigger machine, otherwise this one is fine.

And keep doing this until you’ve reached the amount of people live you think you need. This is what most people will do, as you can see from the Titanfall 2 open beta that’s happening this weekend, even the big companies have to perform load tests in their environments.

Thanks a lot for your advice, Mauricio.

My project is about a collection of escape rooms where the users will be able to play online with their friends. The project is a Facebook app, so the client works with WebSockets in WebGL and it’s done in Unity.

Another thing I will have to face soon is how to deploy the war file here. I’ve tested the server as a single thread run through the shell and I’ve also tested the war file through NetBeans service, but I’ve yet to test it on a hosting service.