<@U0BN9C0HM> there are a couple of reasons for thi...
# http4k
d
@krtko there are a couple of reasons for this: 1. Chiefly, the Netty backend isn't one that we've actually seen used in a production environment - personally I tend to go for: - sunhttp in Dev/tooling env - it starts and stops super fast which helps for testing - undertow in prod, because it is nicer to configure than Netty - there are sources on the net that also recommend this approach for web servers (none to hand) - jetty if I need web sockets - Apache for graalvm as it definitely works out of the box. It's also the one that performs best in the tech empower benchmarks 2. There seems to be some instability with the Netty backend in the benchmarks that we've never got to the bottom of - there's an issue on this: https://github.com/http4k/http4k/issues/141