Micronaut is a software framework for building lightweight, modular applications, and microservices in the cloud. It incorporates existing microservices patterns that developers rely on, helping to eliminate the need to piece together separate tools and frameworks. In this session we will discuss about Micronaut in context of 'Why', 'What' and 'How' .

1. Presented By: Akshat Mathur
Introduction to
Micronaut

2. Lack of etiquette and manners is a huge turn off.
KnolX Etiquettes
Punctuality
Join the session 5 minutes prior to
the session start time. We start on
time and conclude on time!
Feedback
Make sure to submit a constructive
feedback for all sessions as it is
very helpful for the presenter.
Silent Mode
Keep your mobile devices in silent
mode, feel free to move out of
session in case you need to attend
an urgent call.
Avoid Disturbance
Avoid unwanted chit chat during
the session.

3. Our Agenda
01 What is Micronaut?
02 Micronaut AOT Computation
03 Micronaut Offerings
04 More about Micronaut
05 Spring / Micronaut / Quarkus
06 Why Micronaut?
07 Micronaut Core
08 Demo

4. What is Micronaut?
1. A microservices and serverless focused framework
(hence the branding)
2. Also a complete application framework for any type of
Application
3. Dependency injection, aspect oriented programming
(AOP), configuration management, bean introspection
and more..

5. Micronaut AOT Computation
1. All dependency & configuration injection
2. Annotation metadata (Meta annotations)
3. AOP proxies
4. Essentially all framework infrastructure
5. ie. What Spring/CDI do at runtime

6. Micronaut Offerings
1. Microservices
2. Serverless applications
3. Message-Driven applications with Kafka/Rabbit
4. CLI applications
5. Even android applications
6. Anything with static void main(String..args)

7. More about Micronaut
1. An application framework for the future
2. Reflection free, runtime proxy free, no dynamic
classloading
3. Ahead of time (AOT) compilation AOT APIs
4. ... oh and let's you build microservices

8. Spring/Micronaut/Quarkus
● Spring Framework
ᐩ Well established framework
ᐩ Reactive Stack with Spring WebFlux (since v5)
ᐩ Biggest community
ᐩ Most integrations
ᐩ Multi language support (Java, Groovy, Kotlin)
˗ Heavy use of Reflection
˗ Startup time and memory usage not very suitable for
serverless cloud functions
˗ Only experimental support for GraalVM

9. Spring/Micronaut/Quarkus
● Quarkus
❖ Modern cloud native framework
❖ Reactive Stack
❖ Minimal memory footprint and startup time
❖ Based on standards and frameworks (JAS-RX, Netty,
Eclipse Microprofile, …)
❖ GraalVM / Serverless cloud functions
○ Polyglot framework in preview (Kotlin, Scala)
˗ Slower compilation time (AOT)
˗ Smaller community compared to Spring

10. Spring/Micronaut/Quarkus
● Micronaut
❖ Modern cloud native framework
❖ Reactive Stack
❖ Minimal memory footprint and startup time
❖ No byte code modifications during complilation
❖ Removes all levels of reflection usage
❖ GraalVM / Serverless cloud functions
❖ Polyglot framework (Java, Kotlin, Groovy)
○ Similar to Spring
˗ Slower compilation time (AOT)
˗ Smaller community as compared to Spring

11. Why Micronaut?
Features that make Micronaut so well suited for microservices.
● Support for frameworks that implement the Reactive
Streams standard
● Support for messaging systems like Kafka, RabbitMQ,
MQTT, JMS, and Nats.io
● Supports serverless functions for cloud providers like AWS
Lambda, Oracle Functions, Google Cloud Functions, and
Azure Functions
● Supports OpenAPI documentation by creating a YAML file at
compilation time
● GraalVM readiness to further reduce startup time

12. Demo

13. Thank You !
Get in touch with us:
Lorem Studio, Lord Building
D4456, LA, USA