Jooby VS Micronaut

One of the good things about it is that using asynchrony is optional. If you don't have to call out anywhere to build the response, processing can all stay in the handler's calling thread. If you do, you can return a future and have the library handle the async for you.

One downside is that it is based on Jetty which isn't considered the most performant backend. A lib with a similar API but based on Netty is Jooby [1] which scores well in the Techempower benchmarks.

[1] - https://jooby.io/

Jooby and Helidon SE are among the best.

The code snippet gave me a vibe like it was jooby Looks cool, I suggest maybe start incorporating Project Loom virtual threads in the future.

Speaking of backend development, recently I gave Jooby[1] a try after discovering it was one of the world's top performer in Tech Empower's web framework benchmark[2].

Surprisingly enough, it's terribly easy to put together a REST API with Jooby. I wonder why it's adoption rate is so low.

[1] https://jooby.io/

[2] https://www.techempower.com/benchmarks/

Do you need to use Spring btw? If you want to broaden the tool selection I've had great success with i.e Jooby (https://jooby.io/) together with Kotlin coroutines. Another alternative is the KTOR framework.

Jooby I think is the best bet. https://jooby.io/ watch out for jooby dot org I think someone sniped the domain.

Spring Boot or JAXRS. I personally use Jooby a lot which is similar in style to spark but has annotation support and isn't a singleton.

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.