Frameworks solution
Run Quarkus Locally with FlyEnv
Quarkus services run on Java with project-specific databases, Redis, and local proxy configuration. FlyEnv manages those dependencies around the service.
Local project stack
Services FlyEnv can manage around Quarkus
About Quarkus
Quarkus is a Java framework designed around fast startup, low memory use, and cloud-native deployment. It combines familiar Jakarta, REST, persistence, and reactive APIs with extension-based configuration and a developer mode that reloads code and configuration quickly.
Local Quarkus work normally centers on `quarkus dev`, the chosen JDK, and the extensions declared by the project. Dev Services can provision certain containers automatically, but a database, Kafka, Redis, or native build tool should only be started when the application uses it.
Core capabilities
- Dev Mode
- Extension ecosystem
- RESTEasy Reactive
- CDI with ArC
- Dev Services
- Native executable builds
Common use cases
- Cloud-native Java APIs
- Container-first microservices
- Event-driven services
- Low-latency backend endpoints
Quarkus local work follows the selected extensions
A small REST project can run with a JDK alone, while persistence or messaging extensions introduce their own local services.
- JDK and quarkus dev
- Runs continuous testing and live reload during development.
- Extension-backed services
- A configured datasource, Redis client, or Kafka channel may need a matching local service; Dev Services can handle some setups.
- Native build toolchain
- GraalVM or Mandrel is needed only when the project builds and tests a native executable.
Project resources
For installation commands, supported versions, and project-specific configuration, refer to the official Quarkus documentation.
Typical local stack
The exact services depend on the project, its release, and its local configuration. This is a common local setup, not a fixed requirement.
How FlyEnv helps
Select the required JDK
Match the Java runtime to the service.
Keep dependencies local
Run only the configured data services.
Test a local API URL
Configure HTTPS for client integrations.
Set up the local environment
Project installation stays with the upstream documentation. FlyEnv manages the runtimes, databases, web servers, and supporting services around it.
- 1Build or run the service according to Quarkus documentation.
- 2Select the required Java runtime.
- 3Start the configured database and Redis services.
- 4Configure a local proxy and HTTPS when useful.
Related solutions
Ready to run Quarkus locally?
Use FlyEnv to manage the runtimes, databases, web servers, and services around your local Quarkus environment.