@jeffscottbrown talking about Micronaut's full reflection-free Dependency Injection and AOP:
.... and a lot of that has to do with Spring's dependence on runtime reflection. Spring does a lot of run time reflection to discover things about the classes in your application and uses that information to generate a lot of behaviour. That means that the developer has less code to write. Spring can generate this behavior for you.
But it relies on runtime reflection and that runtime the cost of that runtime reflection keeps us from satisfying some of the goals that we had for Micronaut including really fast startup time and small memory footprint,,,
We are extremely excited about Micronaut 1.0 and believe it is at the forefront of the growing movement towards Ahead of Time (AOT) compilation in the Java space. AOT compilation is the next big innovation coming to Java frameworks as it allows Java applications to be optimally built for scenarios such as low-memory footprint Microservices, IoT (yes Micronaut runs on the Raspberry Pi), Serverless, and so on.
Learn how to leverage token propagation in Micronaut to simplify your code while keeping your microservices secure.
We are already planning new security features for 1.1 but I think the Micronaut security portfolio already allows you to build secure apps in an unobtrusive way.
Multi-Tenancy, in software development, is when a single instance of an application is used to service multiple clients (tenants) in a way that each tenants' data is isolated from the other.
Micronaut RC1 ships with multi-tenancy with propagation & database, schema and discriminator modes. It integrates with GORM multitenancy. GORM plays great with Micronaut. I hope Micronaut helps GORM adoption outside Grails and thus Groovy adoption.
Although I recommend you to use GORM in your Micronaut microservices which need persistence, the framework is data access mechanism agnostic. In this Micronaut Guide you learn how to access a database with JPA and Hibernate using Micronaut.