rawhttp VS Armeria

What is complicated about it?? Here's my implementation of it: https://github.com/renatoathaydes/rawhttp/blob/master/rawhttp-core/src/main/java/rawhttp/core/body/ChunkedBodyParser.java

OP doesn't seem to be aware of Armeria https://github.com/line/armeria

Armeria (https://armeria.dev/) is a very underrated framework and does not get enough love, it works fabulously with Kotlin (coroutines support also built-in) and integrates nicely with GRPC, Thrift, etc. The maintainers are very responsive and nice and always helping people out.

Honestly yes? Higher pay, less overtime.

Enjoy https://github.com/line/armeria from a unionized tech company of South Korea!

If you want something really small that simply let's you expose REST APIs using plain Java, without the IoC containers, you might want to check out Javalin, Ratpack or Armeria

Check out Armeria, it's a newer framework from the creator of Netty for micro services and comes with many builtin functionalities for service discovery, logging and fault tolerance. It's getting a lot of adoption from companies like Slack, Doordash, Afterpay and Databricks too. It kind of reminds me of Finagle from the Scala ecosystem in that it supports many different protocols (gRPC, thrift and HTTP).

Armeria which fully supports Reactive Streams and non-blocking IO now powers sttp as a backend.