@spencer Fair enough. I never use h2, usually a local backup if dev. I'm my last company I had a gradle setup that ran on Jenkins, closer to the DB, that would backup the DB, wrap that in a docker image, and upload it to AWS where it was compressed. The job took 3 to 5 min, mostly for the MySQL dump fo dbs in the 4 to 10 GB range, an were compressed to 300 to 500MB. Yeah I don't know what the hangup is getting reloading, but it may or may not have to do with the reflective nature, but also might have to do with the bigger changes in jaca like the modules and what restrictions they add. Don't know the inner workings of OCI, but I think Grails is only a small part, and don't know if it would be reasonable to expect them to take on the hotswap issues. I'll bug @puneetbehl about getting info about whats going on out there. Since I was invited to a weekly meeting with the Grails team, I try to leak out info when I hear it, but those are just slack messages. The team has ramped up again from a low of just Puneet, and a couple of community members, and help where they needed it, to having several more full time members working with Puneet. There are working on Grails 7 which will upgrade Spring Boot to 3.x, Groovy 4, and figuring out what to do with hibernate since the underlying criteria API is gone. Maybe the can take some inspiration from Micronaut data. One thing that delayed the star of that was getting the recent security updates out. From what I understand Grails 6 didn't get spring boot 3 because it was released late in the Grail dev cycle and it would have been a big risk to introduce that and delay a already delayed Grails 6 release. Plus what an upgrade like that can break down stream to the dependent Grails projects.