ktor VS okio

In paralel Jetbrains has created a lot of KMP frameworks that are awesome. One of them is Ktor that helps "create asynchronous client and server applications."

Ktor, a powerful web framework built with Kotlin, offers a lightweight and flexible solution for building web applications. In this article, we will guide you through the process of creating a Ktor project manually using Gradle and SDKMAN!. By following the steps below, you'll have a basic Ktor project up and running in no time.

take a look at http4k and ktor for Kotlin specific frameworks Spring has first class support for Kotlin e.g. the following will give you reactive HTTP endpoints when using spring-webflux (this is what is use at work):

Ktor (Microservices framework by JetBrains)

For Android you should use a more mobile friendly framework like Retrofit or if you use Kotlin you can use the multi-platform Ktor library with it's client module

And last but not least, Ktor Client as our HTTP client. https://ktor.io/ It's a pretty amazing http client library and integrates well with Kotlinx serialization and Coroutines.

Kotlin is going to be great with almost every single JVM server. Spring works well with Kotlin, and is directly supported, but spring is also massive, very bloated. I recommend looking at https://github.com/ktorio/ktor which continues to serve all of my needs very well, integrates fantastically with Kotlin coroutines, and has very fast startup time and very good performance.

For the sake of the test, we use Ktor - the easiest way to do so is to use initializer.

I know you are looking for Spring Boot and/or Quarkus, but have you tried ktor. Just curios if you had a particular reason for choosing the other 2. Disclaimer: I haven't used ktor.

I am involved in the development of Android application which is a rather "thick" mobile client for a Web service. It heavily communicates with the server but also has a lot of inner logic too. So, I decided to use some features of Google Guava library to simplify development process. Here is a list of features I'm very interested in: immutable collections, base utils, collection extensions, functional programming sugar and idioms (common.collect and common.base), primitives utilities (common.primitives), hashing utilities (common.hash), concurrent utils (futures and AsyncFunction). Things I don't want to use in Android: common.cache (see question below), common.eventbus (we have better Android specific libs for this, such as Otto), common.io (we can use okio for Android now).

Yeah Kotlin's own standard library is a lot smaller than Java's currently so you'll need to use something third-party for this. Okio is a popular option https://square.github.io/okio/ it has a Buffer type which is pretty similar to Java's ByteBuffer

Use okio, it is Multiplatform now. I use this for my own library KStore

For networking, file IO, and streams in general, there's Korio and for Java; for just networking, there's LiteNetLib for C#; for what looks like data streams in general, there's Okio also for Java; and Tokio for multi-threaded IO in Rust.

Okio is nice for input/output streams, and sockets.

Sounds like you want https://square.github.io/okio/

On JVM, there is plenty of existing solution already on for multiplatform uses I'd suggest checking amazing Okio library by Square, that seems to cover most of basic use-cases.

I think the main multiplatform library for I/O currently is okio, https://github.com/square/okio. As for compression, you should probably create an expect class for the compressor and use platform specific calls for actual compression. Take a look at https://kotlinlang.org/docs/mpp-connect-to-apis.html.