ktor VS Lombok

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.

The above class maps the json data to a java object we can work with. We use Lombok to generate constructors, getters and setters for our code and the Jackson Project to handle serialization and deserialization of json to pojo . We know the response is an array of objects representing the coffee and so above data structure is fit for this.

Almost a decade ago, I started reducing my boilerplate (and saving time with Lombok. It made my life much easier, simple as that. Ever since I've been looking into finding the smoothest solutions for saving time rather than handling all of it myself.

Lombok is a widely used library that simplifies Java code. The @NonNull annotation helps enforce non-null parameters, generating appropriate null checks:

Project Lombok

I gotta agree with /u/rzwitserloot I don't see anything in the lombok repo that indicates they have their "own compiler". I see the "reaching into javac internals" but that's it.

i looked into that and found this: https://github.com/projectlombok/lombok/issues/2310

Funny enough; /u/rzwitserloot is the author of Lombok, one of the most widely used Java libraries in the world. So it's not really some kind of random-ass Redditor they're having a discussion with either.

This removes the need to add the 'Project Lombok' library (and going through a phase of installing it in your Eclipse IDE; old school devs know what I am talking about) and speeds up development time. Java 14 added a new feature of 'Records' which allows you to do the same, but it doesn't offer a 'copy' method to ease your object creation and also enforces the 'final' keyword for variables making them immutable.

I get the main criticisms of Java, i.e. its verbosity and the requirement for a lot of boilerplate code, and understand why some people switched to Kotlin. But by using libraries such as lombok you can get rid of most of it and suddenly the incentives for switching aren't that big anymore. And in the end it's all JVM bytecode anyways.

I usually use this... https://projectlombok.org/