[amarant]

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/

[invokestatic]

Another vote for Micronaut. I’ve moved a Vert.x project to it recently. I love it. I will say though there are a lot of footguns and the wide variety of choices e.g. for persistence, views, etc make it hard to figure out the “right” way to do things. But the framework just really clicks for me.

[amarant]

I kinda liked the freedom to choose persistence myself, it was one of the things that enabled us to choose it at Mojang, since at the time it wasn't clear if we were going to migrate to a different cloud or not, being able to replace the persistence layer was essential.

As for footguns, I agree there are plenty, but in my experience at least, fewer than in most Frameworks I've used.

Didn't use views much, we built a JSON API, so there wasn't much need for it.

One thing I really liked about it was that it was so easy to get in touch with the Devs, and they so quick to fix things!

We started implementing our API with it before they released 1.0, and as such there were plenty of bugs in the beginning. Quite frequently we submitted a bug report, and there'd be a new version released the same or the next day with a fix for it! Very impressive!

I might've had bad luck with the team where I used vert.x but I've seen a few things in there I would categorize as foot-howitzers, I guess it's just hard to create a framework that can be used for anything without also enabling users to blow their feet off.

Sorry about the rambling comment, just happy to share my thoughts with a fellow Micronaut fan <3