This project was created to study differences between Quarkus and Spring
- Native build is awesome! Besides to take so long to build the application, it runs below 5 seconds
- You don't even need GraalVM installed, in the project has a
Dockerfile.native
that runs natively for you
- Sorry, I configure
compose.yaml
using Mac, not tested in Linux and Windows environments
./gradlew build && docker compose up -d --build && docker logs nbascoring -f
Native
./gradlew build -Dquarkus.package.type=native -Dquarkus.native.container-build=true && docker compose up -d --build && docker logs nbascoring -f
NOTE: Quarkus now ships with a Dev UI, which is available in dev mode only at http://localhost:8080/q/dev/.
The application can be packaged using:
./gradlew build
It produces the quarkus-run.jar
file in the build/quarkus-app/
directory.
Be aware that it’s not an über-jar as the dependencies are copied into the build/quarkus-app/lib/
directory.
The application is now runnable using java -jar build/quarkus-app/quarkus-run.jar
.
If you want to build an über-jar, execute the following command:
./gradlew build -Dquarkus.package.type=uber-jar
The application, packaged as an über-jar, is now runnable using java -jar build/*-runner.jar
.
You can create a native executable using:
./gradlew build -Dquarkus.package.type=native
Or, if you don't have GraalVM installed, you can run the native executable build in a container using:
./gradlew build -Dquarkus.package.type=native -Dquarkus.native.container-build=true
You can then execute your native executable with: ./build/nba-scoring-quarkus-1.0.0-SNAPSHOT-runner
If you want to learn more about building native executables, please consult https://quarkus.io/guides/gradle-tooling.
- SmallRye Reactive Messaging - Kafka Connector (guide): Connect to Kafka with Reactive Messaging
Use SmallRye Reactive Messaging