http4k-connect VS Micronaut

http4k-connect is a set of lightweight (zero-reflection) API libraries for connecting to popular third-party cloud services using http4k clients, along with Fake implementations for usage during local testing. It is based around the Connect pattern, which allows you to express client-side adapters in modular and composable way.

Great stack! Just out of interest , any reason you don't use Http4k connect for your AWS needs?

TBH, the official SDK dynamo client library isn't great for either. If you're looking for something lightweight, you could try http4k-connect - the dynamo client API is much nicer, does type-safety by plugging into the http4k lens system, and is zero reflection (using Moshi and generated adapters), which means you can simply cross compile to GraalVM. We're using it for native Kotlin Lambdas using the custom http4k Lambda runtime and it's 🚀🚀🚀. You can also use it backed by the OkHttp client wrapper if you want.

Micronaut has a share of the space too.

https://micronaut.io/

However, you’re right that Spring Boot has the lions share of the Java ecosystem.

I've used vert.x in a big project once. I don't ever want to do that again. Performance is pretty good, but the developer experience is beyond clunky.

My current favourite Java server framework is Micronaut.

Great performance and easy to develop for!

https://micronaut.io/

I wonder how much you'd save with Micronaut: https://micronaut.io/

> Micronaut is a software framework for the Java virtual machine platform. It is designed to avoid reflection, thus reducing memory consumption and improving start times. Features which would typically be implemented at run-time are instead pre-computed at compile time.

https://en.wikipedia.org/wiki/Micronaut_(framework)

I don't think you'd go down to 9, but something like 20-30 could be doable.

I'd like to introduce my project. It is called mlfx. It can compile FXML ahead of time. It is basically an annotation processor, which internally uses Micronaut framework's AST abstraction and compiles fxml files directly to JVM bytecode. This decreases UI load time and also helps with native-image reflection configs. It also has some compliance tests that load compiled code and check resulting object graph against one loaded by javafx-xml. It also has some drawbacks now, but, please, read README. Now I'm successfully using it in two production projects.

https://micronaut.io/ https://quarkus.io/

when it comes to full stack frameworks, Micronaut(https://micronaut.io/) is actually good and pleasant to work with.

For the server Quarkus and Micronaut might be interesting besides Spring Boot. Quarkus is more popular and backed by RedHat (so probably here to stay).

🥇 Spring Boot 🥈 Quarkus 🥉 Micronaut 🏅 Ktor 🏅 http4k

Spring boot is still The King. Although I've not done more than hello world with Micronaut, it might have easier learning curve than Spring (and concepts are similar to Spring so you can carry over later to learn Spring). It could also be a useful skill in world of microservices these days.