Quarkus + Maven REST API Starter
Quarkus, Java, Maven, JUnit 5, and REST Assured form a backend service configuration where the generated project is centered on a backend service. Better Fullstack can scaffold this exact compatibility-checked selection.
01 / selection
Stack at a glance
| Role | Technology | Repository description | Scope |
|---|---|---|---|
| Backend | Quarkus | Cloud-native Java framework optimized for fast startup and lower memory use | Primary backend |
| Language | Java | Classic Java sources | Project-wide |
| Database | None | Skip database integration | Project-wide |
| ORM | None | Skip Java ORM/database layer selection | Project-wide |
| Authentication | None | Skip Java authentication library selection | Project-wide |
| API | None | REST controllers only | Project-wide |
| Build tool | Maven | Convention-based Java build tool with Maven Wrapper support | Scoped to the backend |
| Testing | JUnit 5 | Modern Java unit testing platform | Scoped to the backend |
| Testing | REST Assured | DSL for HTTP API and REST endpoint tests | Scoped to the backend |
02 / architecture
How the pieces fit
- The generated stack is centered on a backend service with no browser frontend.
- Maven is scoped to the backend.
- JUnit 5 is scoped to the backend.
- REST Assured is scoped to the backend.
03 / output
What gets generated
The virtual generator produced 13 files across 14 directories. The output is a single-directory project.
Top-level entries
- ./.env.example
- ./.gitattributes
- ./.gitignore
- ./.mvn
- ./AGENTS.md
- ./CLAUDE.md
- ./README.md
- ./mvnw
- ./mvnw.cmd
- ./pom.xml
- ./src
Representative files
- README.md
- pom.xml
- src/main/java/com/example/myapp/Application.java
- src/main/java/com/example/myapp/resource/GreetingResource.java
- src/test/java/com/example/myapp/RestAssuredHttpTest.java
- .env.example
- .gitattributes
- .gitignore
04 / create
Create command
This is the canonical Bun command generated for the selection.
bun create better-fullstack@latest my-app --ecosystem java --database none --java-web-framework quarkus --java-build-tool maven --java-orm none --java-auth none --java-api none --java-logging none --java-libraries none --java-testing-libraries junit5 rest-assured --email none --observability none --caching none --search none --ai-docs claude-md agents-md05 / builder
Open in the builder
- eco
- java
- db
- none
- orm
- none
- au
- none
- jwf
- quarkus
- jtest
- junit5,rest-assured
06 / checks
Compatibility notes
Compatibility checked against Better Fullstack types version 2.8.0.
The generated record has 0 graph issues and 0 disabled selected options. This is a compatibility check, not a claim that this exact scaffold received a runtime smoke verification.
- Database is intentionally set to none.
- Java ORM / Database is intentionally set to none.
- Java Auth is intentionally set to none.
- Java API Layer is intentionally set to none.
07 / fit
When to choose this shape
Choose this shape when the generated project should expose backend functionality without a browser frontend.
08 / next
Related stacks and guide
Need a walkthrough? Read the related stack guide.
09 / faq
Questions
Is this combination supported?
It passes the repository's compatibility analysis, selected-option checks, stack graph validation, project schema parsing, and virtual generation. That result is described here as compatibility checked.
Does it generate one app or separate parts?
The generated project is centered on a backend service. The actual generated output uses a single-directory layout.
How can I customize the selection?
Open the generated builder link above. Its query parameters reproduce this selection, and the builder can change compatible options before generating a new command.