https://github.com/teedjay/quarkus-and-microstream
Testing MicroStream using Quarkus and Java 17+
https://github.com/teedjay/quarkus-and-microstream
Last synced: 3 months ago
JSON representation
Testing MicroStream using Quarkus and Java 17+
- Host: GitHub
- URL: https://github.com/teedjay/quarkus-and-microstream
- Owner: teedjay
- Created: 2022-01-09T16:27:16.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2022-01-09T21:03:00.000Z (over 4 years ago)
- Last Synced: 2025-03-03T04:41:53.542Z (over 1 year ago)
- Language: HTML
- Size: 28.3 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# quarkus-and-microstream
Template for testing the following combinations :
- [x] Java 17+
- [x] Quarkus
- [x] [MicroStream](https://github.com/microstream-one/microstream)
- [x] Using Java `records` (see [`--add-exports java.base/jdk.internal.misc=ALL_UNNAMED`](https://docs.microstream.one/manual/storage/faq/java-features.html))
- [x] Use JimFS for in-mem storage (to prevent `storage` folder to be stored on disk)
- [x] Simple Qute based [HTML view](http://localhost:8080/pokedex)
## Notes about `storage` folder ...
Without JimFS default will create a filesystem folder locally called `storage`, the contents of this must be deleted manually betweens runs.
## Running the application in dev mode
You can run your application in dev mode that enables live coding using:
```shell script
./mvnw compile quarkus:dev
```
> **_NOTE:_** Quarkus now ships with a Dev UI, which is available in dev mode only at http://localhost:8080/q/dev/.
## Packaging and running the application
The application can be packaged using:
```shell script
./mvnw package
```
It produces the `quarkus-run.jar` file in the `target/quarkus-app/` directory.
Be aware that it’s not an _über-jar_ as the dependencies are copied into the `target/quarkus-app/lib/` directory.
The application is now runnable using `java -jar target/quarkus-app/quarkus-run.jar`.
If you want to build an _über-jar_, execute the following command:
```shell script
./mvnw package -Dquarkus.package.type=uber-jar
```
The application, packaged as an _über-jar_, is now runnable using `java -jar target/*-runner.jar`.
## Creating a native executable
You can create a native executable using:
```shell script
./mvnw package -Pnative
```
Or, if you don't have GraalVM installed, you can run the native executable build in a container using:
```shell script
./mvnw package -Pnative -Dquarkus.native.container-build=true
```
You can then execute your native executable with: `./target/quarkus-and-microstream-1.0.0-SNAPSHOT-runner`
If you want to learn more about building native executables, please consult https://quarkus.io/guides/maven-tooling.
## Related Guides
- RESTEasy Reactive ([guide](https://quarkus.io/guides/resteasy-reactive)): Reactive implementation of JAX-RS with additional features. This extension is not compatible with the quarkus-resteasy extension, or any of the extensions that depend on it.
## Provided Code
### RESTEasy Reactive
Easily start your Reactive RESTful Web Services
[Related guide section...](https://quarkus.io/guides/getting-started-reactive#reactive-jax-rs-resources)
### RESTEasy Reactive Qute
Create your web page using Quarkus RESTEasy Reactive & Qute
[Related guide section...](https://quarkus.io/guides/qute#type-safe-templates)