{"id":76573,"date":"2020-04-03T13:42:25","date_gmt":"2020-04-03T11:42:25","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/nativnaya-kompilyacziya-v-quarkus-pochemu-eto-vazhno"},"modified":"2020-04-03T13:42:25","modified_gmt":"2020-04-03T11:42:25","slug":"nativnaya-kompilyacziya-v-quarkus-pochemu-eto-vazhno","status":"publish","type":"post","link":"https:\/\/prohoster.info\/da\/blog\/administrirovanie\/nativnaya-kompilyacziya-v-quarkus-pochemu-eto-vazhno","title":{"rendered":"Native compilation in Quarkus \u2013 why it matters","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Hello everyone! Here\u2019s the second post in our series on Quarkus \u2013 today we\u2019ll talk about native compilation.<\/p>\n

\"Native
\n
\nQuarkus<\/a><\/noindex> \u2013 it\u2019s a Java stack focused on Kubernetes<\/a><\/noindex>. And while there\u2019s still much to be done here, we\u2019ve worked through a lot of aspects, including JVM optimization and various frameworks. One of the features of Quarkus that has sparked keen interest among developers is the comprehensive seamless approach to transforming Java code into executable files for a specific operating system (the so-called 'native compilation'), similar to C and C++, where such compilation typically occurs at the end of a cycle consisting of building, testing, and deploying.
\n<\/a><\/noindex>
\nAnd although native compilation, as we will show below, is important, it should be noted that Quarkus actually works quite well on a standard Java machine using OpenJDK Hotspot, thanks to the performance improvements we\u2019ve implemented throughout the stack. Therefore, native compilation should be considered an additional bonus that can be used at will or necessity. In fact, when it comes to native images, Quarkus significantly relies on OpenJDK. Furthermore, the warmly received development mode provides near-instant testing of changes due to the advanced capabilities of dynamic code execution implemented in Hotspot. Additionally, when creating native images, GraalVM utilizes the OpenJDK class library and HotSpot capabilities.<\/p>\n

So why is native compilation necessary if everything is already well optimized? This is the question we will attempt to answer below.<\/p>\n

Let\u2019s start with the obvious: Red Hat has extensive experience in optimizing JVMs, stacks, and frameworks throughout the project\u2019s development. JBoss<\/a><\/noindex>, including:<\/p>\n