Armeria VS kotlinx.serialization

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.

Have you tried this:? https://github.com/Kotlin/kotlinx.serialization/blob/master/docs/serializers.md

Regardless, I followed the documentation to register List for polymorphic serialization and my static code analysis does not seem to be happy with it.

I think kotlinx.serialization might come close, but looks like custom Encoders and Decoders are still experimental.

This example will not work on a multiplatform project. you are using gson, gson runs only on jvm, you should use https://github.com/Kotlin/kotlinx.serialization for the json parsing

This is the issue to +1 https://github.com/Kotlin/kotlinx.serialization/issues/1931

Fun fact, kotlinx.serialization had a release just recently which makes it come with some bundled proguard rules to make this experience easier. Yes you'll still have issues if you're using things via reflection and try to serialize things that proguard deemed unused and removed them, but it's a step forward https://github.com/Kotlin/kotlinx.serialization/releases/tag/v1.5.0-RC

Kotlin Serialization

Kotlin Serialization is also a newer option, but doesn't have as much traction.

``` see the docs