This document introduces Quarkus, an open source Java framework for building container-native microservices. Quarkus uses GraalVM to compile Java code ahead-of-time, resulting in applications that are up to 10x smaller and 100x faster to start than traditional Java applications. It is optimized for Kubernetes and serverless workloads. Quarkus achieves these benefits through ahead-of-time compilation using GraalVM, which analyzes code statically and removes unused classes and code to generate efficient native executables.

1. Introduction to Quarkus:
A Container-First Cloud Native
Framework
Georgios Andrianakis, Red Hat

5. But Java has been showing its age...

6. Memory Hog
🐷

9. Slow Startup
🐍

10. Serverless Adoption
https://serverless.com/blog/2018-serverless-community-survey-huge-growth-usage

11. So who is this Quarkus—
and what’s all the fuss?
Up to 10x smaller, 100x faster
Seriously.

12. Imperative and
reactive
Serverless
Live reload
Microservices
Fat jars
and native
executables
Optimized for
JAX-RS & JPA
(Hibernate) …

13. Kubernetes Native

14. Image:
quay.io/images/custservice:1.1.0
Replicas:
20
Labels:
customerservice=prod,ci_build=1213
ConfigMap:
cust_config

15. But how is this achieved?

16. Traditional Java apps (both app server and fat-jar stacks)
● Tons of classes loaded during boot time
○ Unused later on
○ Occupy a lot of memory
● Reflection used extensively
XML Parsers, Annotation models….

17. Quarkus
Do as much as possible at build time
● Annotation processing
● Configuration parsing
● Throw away all classes that are not needed at runtime
● Avoid runtime reflection as much as possible
Output: generated classes

19. GraalVM

20. AoT with GraalVM

21. AoT with GraalVM
● Static Analysis
● Closed world assumptions
● Dead code elimination

22. GraalVM Limitations
● Dynamic classloading
○ Creating, reloading classes at runtime is not possible
● JVMTI, JMX
○ No agents
● InvokeDynamic, MethodHandles
○ But lambdas are supported

23. GraalVM Limitations
● Reflection
○ All targets of reflection need to be known
● Dynamic Proxies
○ All classes that will get proxied at runtime need to be
declared
● Classpath resources
○ All resources to be included must be declared

24. GraalVM Limitations
Example of manual invocation:
native-image -jar target/app.jar -H:ReflectionConfigurationResources=reflection_config.json
-H:Name=name
--delay-class-initialization-to-runtime=io.netty.handler.codec.http.HttpObjectEncoder
Quarkus shields you from all GraalVM peculiarities!

26. Demo time!

27. Thank you!
Twitter: @geoand86
Further reading
• http://quarkus.io
• https://developers.redhat.com/blog/2019/03/07/quarkus-
next-generation-kubernetes-native-java-framework/
• http://in.relation.to/2019/03/08/why-quarkus/