I want to create a simple cross-browser multiplayer game (chess or card game) that will communicate with a server sockets Using
I have some intermediary knowledge of Ruby language, but I am not sure whether this is a good solution for a multi-client server, so there is an idea that Node.js or Socket.io can be a better one. I know that Java or C ++ can be very good for a job, but none of them is very easy for me, so this is why I'm heading to server-side javascript.
My question is, do you think this is the best solution for a project like this? What could be the best server-side technology, on which I would create a whole game and communication logic? Perhaps some combination of them? Any comment about speed, server load, hosting solution and speed of development for each technology will be greatly appreciated.
If you're comfortable with JavaScript, you have the node. J. S. There is nothing to lose by giving: the learning curve will be soft. This is a very good server technology
The only loss with the Node JS will definitely not be on the scale like Java. Sure. This is usually okay for web applications because you can throw the caching layer in front (reverse proxy), which makes it a lot less. I think this will not be appropriate for your application, because the state of the game will change a lot.
Nodes can "scale" JS, however by spinning more examples. If a server can easily accommodate more than one "world of sports", then it is straightforward. If you need to split the gameworld across multiple servers, then the server has to cooperate. However, beware of this scenario, it is not as easy as it appears before: it is called "multi master" problem and is one of the starved internet monsters
Comments
Post a Comment