This repository showcases Spring and Quarkus projects implementing GraalVM native compilation, with performance comparisons against traditional JVM versions.

The goal of this project is to evaluate the benefits and challenges of native image compilation in Java frameworks, focusing on Spring and Quarkus.

• quarkus-native: Adds support for Quarkus Native using GraalVM, enabling the application to be compiled and run as a native binary, improving startup time and memory usage.
• quarkus-reactive-native: Implements reactive programming with Quarkus, including reactive RESTful endpoints, services, and repositories using Uni and Multi, enhancing the application's reactive capabilities.
• spring-native: Adds support for Spring Native with GraalVM, allowing the application to be compiled and run as a native binary, improving startup time and memory usage.
• spring-webflux-native: Introduces reactive programming with Spring WebFlux, including reactive endpoints using Flux and Mono, a reactive repository with R2DBC, and Flyway for database migrations, enhancing the application's reactive capabilities and ensuring smooth database migrations.

We measure and compare the following metrics:

• Startup time
• Memory usage
• Throughput
• Response time

• GraalVM [version]
• Maven or Gradle
• [Any other tools]

[Provide basic instructions or link to detailed docs]

[Summarize key findings or link to detailed results]

We welcome contributions! Please see our Contributing Guide for details.

This project is licensed under the [choose a license] - see the LICENSE file for details.

• [Any acknowledgments or credits]