java-quarkus-patterns

Implement Quarkus CDI services and REST endpoints with Panache repositories.

6|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/wesleyosantos91/multi-agents --skill java-quarkus-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: java-quarkus-patterns
Source: https://github.com/wesleyosantos91/multi-agents/tree/main/devin/.devin/skills/java-quarkus-patterns
Command: npx skills add https://github.com/wesleyosantos91/multi-agents --skill java-quarkus-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of teams repeatedly reinventing Quarkus architecture and production-ready implementation patterns, leading to inconsistent code, slow startup behavior, and fragile integrations.

Core Features & Use Cases

  • Quarkus build-first structure: promotes build-time configuration to achieve faster startup and predictable runtime behavior.
  • CDI + RESTEasy Reactive idioms: provides scoped beans and clean JAX-RS endpoint patterns with transactions and validation.
  • Production integration patterns: includes exception mapping, Panache repository usage, MicroProfile REST Client wiring, and fault tolerance with retries/circuit breakers/timeouts.
  • Operational readiness: standardizes liveness/readiness health checks, configuration profiles, and optional Lambda deployment wiring.
  • Dev productivity: enables dev mode workflows with hot reload and Dev UI.

Quick Start

Tell the AI to generate a Quarkus project skeleton for a new Order API using CDI services, RESTEasy Reactive endpoints, Panache repositories, a MicroProfile REST Client with retries and circuit breaker, and liveness/readiness health checks.

Frequently Asked Questions about java-quarkus-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement fault tolerance with retries and circuit breakers in a Quarkus REST application?

Implement fault tolerance in a Quarkus REST application by applying MicroProfile Fault Tolerance annotations to your CDI beans. This pattern uses retries, circuit breakers, and timeouts to ensure resilient runtime behavior for external service integrations.

What is the best way to structure Panache repositories and RESTEasy Reactive endpoints in Quarkus?

The best way to structure Panache repositories and RESTEasy Reactive endpoints is to follow Quarkus build-time-first configuration with correctly scoped CDI beans. This ensures clean JAX-RS endpoint wiring, proper transactional boundaries, and predictable startup.

How do I integrate external APIs using MicroProfile REST Client in a Quarkus project?

Integrate external APIs in a Quarkus project by wiring a MicroProfile REST Client to your CDI services. Standardized production patterns include exception mapping and fault tolerance annotations to handle external service failures gracefully.

Can I use Quarkus patterns to standardize liveness and readiness health checks for production deployments?

Yes, you can use Quarkus patterns to standardize liveness and readiness health checks for production deployments. These operational readiness patterns also include configuration profiles and optional Lambda deployment wiring for consistent runtime behavior.

Why does my Quarkus application have slow startup and fragile service integrations?

Slow startup and fragile integrations often occur when teams reinvent Quarkus architecture instead of using build-time-first configuration. Adopting standardized CDI scopes, Panache repository patterns, and MicroProfile REST Client wiring resolves these inconsistencies.

Do I need specific CDI scopes for building REST endpoints with Quarkus RESTEasy Reactive?

Yes, adhering to correct CDI scopes is required when building REST endpoints with Quarkus RESTEasy Reactive. Correct scoping ensures proper transactional boundaries and aligns with the Quarkus build-time-first philosophy for faster startup.