My problem is as follows:
I'm developing an online game with the requirement of being able to handle
thousands of requests every second.
The frontend consists of web server(s) exposing a rest api. These web servers
in turn communicate with a game server over TCP. When a message arrives at the
Quick smoke test. How big are your requests/responses? You mention
REST, which implies they're going to be based on HTTP. I would expect
you would have some idea of the rough size. Multiply that by 50,000,
and see whether your connection can handle it. For instance, if you
have a
(You're using Google Groups, which means your replies are
double-spaced and your new text is extremely long lines. Please fix
this, either by the fairly manual job of fixing every post you make,
or the simple method of switching to a better client. Thanks.)
My point was just about
Den lördagen den 18:e januari 2014 kl. 13:13:47 UTC+1 skrev Asaf Las:
On Wednesday, January 15, 2014 8:37:25 PM UTC+2, phi...@gmail.com wrote:
My problem is as follows:
2) The network layer of the game server runs a separate process as well,
and my intention was to use
