You may know it from delivering the Grails framework. How are both going?įor Micronaut, the key maintainer and supporter is Object Computing, Inc. Who’s backing the project?īefore choosing a framework, the critical thing is to know who is backing a given tool, whether it is alive, and how big its community is. However, with both, we can still create a monolith application.

The frameworks provide extensions making the task easier. Developing microservices and deploying them on a cloud platform gained momentum some time ago. That feature boost development and deployment of cloud-native applications and serverless deployments - a thing that cannot be overestimated nowadays.Īnother concern addressed is the rapid development of microservices with a strong focus on cloud deployment. The possibility of creating native images using GraalVM out of the box is the next feature supporting the rapid startup of applications developed with the frameworks. Both these advantages make a difference, especially when running services in the cloud - we can buy a cheaper machine running our apps. There are two major advantages of this: smaller memory footprint as we don’t need to store reflection metadata and faster runtime since the compilation process takes care of dependencies injection. They achieve this by using compile-time dependency injection and aspect-oriented programming. The most important aspects presented by both frameworks are lower memory consumption and rapid startup time. Why were they created? What issues do they address? I want to go through a broad spectrum of their features to see what they offer.īoth aspire to be modern frameworks, having support corresponding to the current challenges of writing JVM applications. As you may have guessed, the story is about two frameworks: Micronaut and Quarkus.

Quarkus with kotlin