9 engineers on Hacker News describe using Jetty first-hand: 1 endorse it, 2 regret it, 0 are mixed.
“it has severe quality issues... At one point we had to fork Jetty to fix critical problems, never again.”
regret · production · keypusher · 2015-04-08 · source ↗ · wrong label?“But the developers did. Oh they were about 5x as productive afterwards. With no missing features.”
endorse · production · lukaseder · 2014-11-27 · source ↗ · wrong label?“We run Java on Jettys for most of the things for our app... the Jettys keep going out of memory every now and then.”
regret · production · rehack · 2013-01-29 · source ↗ · wrong label?“At Addepar, we use plain Java. A REST API can be served with Jetty + Jersey.”
neutral · production · dcposch · 2015-09-30 · source ↗ · wrong label?“we switched to JAR/Docker deployments for Scala some time ago with Jetty instead of WARs”
neutral · production · _Codemonkeyism · 2015-09-11 · source ↗ · wrong label?“I started out with gradle and embedded jetty”
neutral · personal · sghill · 2013-12-11 · source ↗ · wrong label?“Server-side, we use Spring Framework running inside a Jetty servlet container.”
neutral · production · Eduard · 2013-11-27 · source ↗ · wrong label?“Apache was not the problem there, as it was simply proxying over to Jettys.”
neutral · production · rehack · 2013-09-07 · source ↗ · wrong label?“We use Java, MongoDB, Hadoop and embedded Jetty at MetaBroadcast”
neutral · production · johnayres · 2010-11-23 · source ↗ · wrong label?