ktor VS KEEP

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.

Check https://ktor.io it's from JetBrains and amazing.

`Either foo()` and `Foo foo() throws MyError` and are pretty much isomorphic.

https://github.com/Kotlin/KEEP/blob/master/proposals/stdlib/...

Nice. So for example, it looks like Kotlin has a nearly identical feature at the language level which will be optimizable when Valhalla ships: https://github.com/Kotlin/KEEP/blob/master/notes/value-class...

> In the future, in a Valhalla-capable JVM, JVM primitive classes will enable efficient representation of Kotlin value classes with an arbitrary number of underlying fields on JVM.

Most other languages agree that checked exceptions are not good by not having them.

As for alternatives, Try/Result and similar monads have decent adoption even in Java, but personally I quite like the Kotlin philosophy [1] to not have generic error containers and either use runtime exceptions or make failures of the return type.

[1] https://github.com/Kotlin/KEEP/blob/master/proposals/stdlib/...

If you want to read more and don't want to google it: https://github.com/Kotlin/KEEP/blob/data-objects/proposals/data-objects.md

Under the hood: https://github.com/Kotlin/KEEP/blob/master/proposals/coroutines.md .

you can check more here

You can use explicit API mode, then everything needs explicit visibility