May 30th, 2018 Micronaut 1.0.0.M1 released
First milestone of 1.0.0 for Micronaut. See documentation.
May 23rd, 2018 Micronaut Open Sourced
Today, it is with great pleasure that we open source Micronaut on Github.
Micronaut represents a significant advancement in how a range of application types – with a particular focus on microservices – are built for the JVM.
By leveraging the lessons learned building the Grails framework, we have built a toolkit that encompasses all the modern features developers have come to expect from a framework, including dependency injection, AOP, configuration management, and more.
With Micronaut, however, we’ve greatly reduced the runtime overhead – in terms of memory consumption and startup time – found in traditional frameworks. This is achieved through the use of annotation processors that pre-compile all the necessary metadata and information needed to run your application ahead of time, eliminating the need for reflection and cached reflective metadata at the framework level.
Micronaut also features both an HTTP client and an HTTP server built on Netty, plus a range of tools to aid deployment into a cloud environment.
Micronaut supports building applications in Groovy, Java, and Kotlin. Its design takes heavy inspiration from Spring and Grails to ensure that it is as simple as possible for developers to become fully proficient with the framework.
For more about these features, view the comprehensive Snapshot documentation.
Next week at Gr8Conf Europe in Denmark, our team will deliver numerous talks and workshops on Micronaut for those interested in getting a head start using the Framework. (Find out where else you can see Micronaut in action.)
We will also be releasing the first milestone of Micronaut 1.0 next week, which will be followed quickly with regular milestone releases and ultimately a GA release later this year.
Over the next few months, we will be working diligently to build out the Framework’s features and capabilities, so please stay tuned and feel free to submit your ideas and suggestions to us.
With warm regards, Graeme Rocher