A modern programming language that makes developers happier.

kotlinlang

What you guys don't like about Ktor server?

What I don't like:
• Lack of uniform HTTP API + different classes for request/response depending on whether you are building a client or server. That limits the ability to plug clients and servers for testing (Server as a Function).
• Enforced async + coroutine usage. Again, this makes testing and debugging harder in exchange for runtime characteristics most applications won't benefit from (especially in serverless environments).
• DSL-esque API
What I like:
• The documentation is great
• Extensions are simple and explicit via `install` calls
• Cross-platform
• It's not Spring
I haven't used Ktor in production because I never had to, so I do not know how much trouble it is for real apps. That's another reason we built http4k: there are already great battle-tested HTTP client/server implementations out there that we felt we only needed a Kotlin-first abstraction on top of them.

What Ivan said, although I don't mind the DSL-esque API.

Also:
• lacks good OpenApi integration
• doesn't integrate with Moshi (but supports Gson for some reason)
• forces you to use kotlinx.serialization for its resource-ful builder
• the test client is a bit annoying to use