A
A
AlexCodly2014-11-04 10:40:53
Java
AlexCodly, 2014-11-04 10:40:53

Choosing a client-server java framework for a highly loaded application?

The server will work with the database at the request of the client.
The client will send requests and receive responses.
I came up with something like this:
Commands to the server
"$signup [email protected] pass1234" (the server can return "$err" or "$auth_token QWERTY123456ASD789" ).
"$get example_article99" (the server returns this article or "$err" from the database).
"$put QWERTY123456ASD789 example_article99" (an article or "$err" is added to the database).
"$update QWERTY123456ASD789 example_article99" (an article or "$err" is being updated in the database).
Everything happens in one cycle: the client asks - the server answers and the connection is closed.
How stable and productive is such a solution (> 1000 simultaneous connections)? I also want to add c2dm and take a token from there (if possible?). Maybe it's better to use Netty or quickserver?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
I
Ivan Smirnov, 2014-11-13
@AlexCodly

To be honest, I did not understand why you need a framework at all.
1000 connections is not so much, and it will work fine in pure Java without asynchrony. 10000 is already better asynchronously. You can look at akka in this regard.
For the web (if you need it), you can use play! or grails (some would say spring).

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question