DEV Community

Discussion on: Opinionated take on Java Microservices Frameworks

Collapse
 
cesdperez profile image
César Daniel Pérez

Nice article!

At our company, we'll be writing a new backend from scratch and we'll have to take this same decision.
A couple additional factors I'd like to evaluate are the ease and performance interacting with DBs (specially using reactive stacks) and the GraalVM native image alternatives.

I'm curious on how has been your experience with Micronaut in these months.

Collapse
 
dansiviter profile image
dansiviter

I wouldn't use it on another project:

  • There is far too much 'magic' which obfuscates what is actually happening and it doesn't generate the intermediate source classes to debug,
  • Hibernate integration is rough, especially the configuration,
  • Basic functionality doesn't exist and when you raise bugs or feature requests the maintainers are dismissive and too eager to close without discussion.

As for reactive... ignore it and wait for Java 19 with Virtual threads. This all but eliminates the scaling benefits of reactive but much easier to diagnose errors.