From what I understand upgrading Spring, and Groovy is really only half the battle, and the Grails team was close to releasing an M1. The other half would be figuring out how to upgrade hibernate under GORM since the criteria API has been deprecated. @mattias_reichel @puneetbehl feel free to correct me if I'm mischaracterizing. I don't think adding Micronaut took a lot of dev time away from keeping up with dependencies. Grails has always lagged behind Spring, and in more recent years Spring has tightened its EOL schedule. I think that team might have shrunk as well. I don't see Micronuat/Microservices as any more dangerous than I see Monoliths, they both have their advantages and disadvantages. I'm using Micronaut now at a startup and it works fine for our purposes, which is more along the lines of "services" than microservices. I think you would write a monolith with Micronaut if you wanted to. I do miss the convention over configuration. Monoliths are not evil, but if let to grow without restriction they can start to cause there own problems in terms of build time and startup. I think there is nothing wrong with starting with a monolith and when time comes splitting off into services/micro services and having a hybrid solution. I don't see Grace as a way forward, I see that more as a step backward, and something that if following your suggestion @giangio would be more likely to fracture this community and hasten its demise. Although I think those thoughts are a bit premature going in any direction as we have not heard anything from @graeme , @jeffscottbrown , the Grails Foundation, or the Unity Foundation: https://grails.org/foundation/index.html As I mentioned this has happened to Grails before when Pivotal dropped funding for Grails and OCI picked Grails up. I don't know how likely that is to happen again, but I would give it a week to two before jumping to any conclusions and evaluate possibilities for the worst-case scenario.