Hi, sorry for thelate response. Please, pay attention that this series is about the migration of an existing Grails application into Micronaut one and I expect you already have your modern frontend created.
You are right that Micronaut is missing some of the rapid application development features that let you create complete applications very quickly but in a long term. all the magic makes the application more difficult to maintain.
If you are looking for a RAD tool based on Micronaut then take a look on MHipster:
The performance wasn't the main reason for the migration. The initial impulse was that we were not able to share the code between our serverless functions and the main application. Even we have created a bridge library there was still some friction, especially on the configuration level. Grails 4 has removed some of the problems but other ones arisen so we decided to remove Grails completely. We are not there yet and this series has been written for my coworkers to help them migrate our applications gracefully.
Yet another reason was that using Grails keeps us a lot behind the newest versions of the libraries — Grails 4 still uses Micronaut 1.x and Groovy 2.x. Using the latest Micronaut and Groovy also allows use to use the latest versions of Java.
If you're looking for some performance comparison, just search for Spring Boot vs Micronaut articles.
