GraalVM Drawbacks

 Building a native image is a complex process involving not only Java Toolset but also C++ Toolset
 Building a native image is significantly slower than a regular compilation
 May go against Dev/Prod parity (https://12factor.net/dev-prod-parity)
 Because native image compilation is a long process, most probably during regular development, you will
execute code on top of HotSpot VM, and you will switch to native image only for production environments
 This means that most of the time, you will develop and test the application under different execution
runtime than on the production
 Effectively, this means that the development environment is less similar to the production environment
 Less mature than regular JVM
 Additional configuration is required for dynamic code like reflection, dynamic proxies, etc.
 Classpath is fixed at build time
 No lazy class loading, everything will be loaded into memory on startup

Spring Native Tutorial 15