ddd4j-quarkus Architecture

Overview

Covers parent, bom, dependencies, extension-parent, auth, data, mq, web, cache, extensions, and samples uniformly, not split per artifact. Choose 3.3.x or 4.0.x first, then read the current source.

When to Use

• Designing or reviewing the ddd4j-quarkus module layout: parent, bom, dependencies, extension-parent, auth, data, mq, web, cache, extensions, samples.
• Deciding which module a new capability or sample belongs in, and which modules it may depend on.
• Checking that runtime and deployment modules are separated per the Quarkus build-time model on either line (3.3.x → Quarkus Platform 3.37.4 / JDK 17 / Maven 3; 4.0.x → Quarkus Platform 3.38.2 / JDK 21 / Maven 4).
• Producing a read-only boundary review with entry points, CDI registrations, and violations.
• Verifying that dependency direction between modules matches the current line's contract.
• Onboarding a developer to where each Quarkus adaptation lives in the ddd4j-quarkus tree.

When NOT to Use

Do not use this skill when: