java - How scalable is Jetty? -
Greetings! I wrote a high scalable HTTP event (Long Voting) server which was using libevent in C / C ++. However, this is a mess, it is rarely portable, and lets it face it: It is C. Be lonely that I have some major problems with mysqlcpp connector (which is full garbage), and libevent some small issues (this may be because I'm using 2.0.1-alpha) Event Server C / C ++, and the actual backend is PHP-FPM if I need to hit me (i.e. there is a new event). All proxy / CGI routing is done through NGNX.
I am arguing about rewriting the whole thing (event server and backend) in Java - I like to use PHP for French-end. I have heard many good things about Jetties, but I am thinking that someone has experience of deploying the real-world highly-concurrent applications working on the Jetties backend. If so, how does this stack compare to an HTTP libevent implentation, or equivalent Erlang and Python server libraries?
I am not interested in the apachebench
criteria so please do not link to them. I'm interested in concurrency and scalability .
Thanks for any insights.
We have voted for JT for a while and we are very happy with it. We were never close, as though JT developers showed up. However, the added overhead of 300-400 concurrent cumulated connections on our low-end servers was hardly limited. There is another article (which is another horrible piece of software).
Comments
Post a Comment