Tomcat or Jetty for Java server application -


suppose have design server process concurrent independent http requests. processing cpu-bound (no database involved).

requests relatively small (1-10k) , latency important (the less better). number of concurrent requests , "rate' (requests per second) still unknown.

we going develop server in java. should use tomcat or should use embedded http server (e.g. jetty) part of application?

either 1 satisfy stated requirements.

tomcat require install - or can embedded; jayan correction. jetty can embedded or run in stand-alone mode. choose on basis.

but if you're setting centralized server, might consider netty on both. nio might throughput. per joakim erdfelt below, jetty uses nio well. thank education , correction. don't know if tomcat has followed suit.


Comments

Popular posts from this blog

Delphi XE2 Indy10 udp client-server interchange using SendBuffer-ReceiveBuffer -

Qt ActiveX WMI QAxBase::dynamicCallHelper: ItemIndex(int): No such property in -

Enable autocomplete or intellisense in Atom editor for PHP -