Armeria VS Play WS

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.

Take a look at https://github.com/playframework/play-ws build.sbt. it is a scala lib built with sbt-assembly to shade dependencies and avoid binary incompatibility. That is the only reason to build a lib with sbt-assembly.

In this example, the code uses Play WS Standalone as a REST client to fetch JSON containing a UUID. Play WS has an asynchronous, non-blocking API based on Future, so you need to provide an ExecutionContext via Akka. That's all the boilerplate at the beginning of this example. Sometimes it will be done for you as when you use Play WS in the context of Play Framework. Nonetheless, you should be aware it has to happen somewhere.