ddd4j-javalin Architecture

Overview

Covers parent, bom, dependencies, core, ddd, auth, data, mq, web, cache, extensions, and testcontainers uniformly. Confirm the maintenance line with ddd4j-javalin-version-selection first, then read the current branch source.

When to Use

• Designing or reviewing the module set — parent, bom, dependencies, core, ddd, auth, data, mq, web, cache, extensions, testcontainers — on any maintenance line (6.7.x, 7.1.x, or 7.2.x).
• Checking dependency direction between modules: adapters may depend on core SPIs, never the reverse.
• Reviewing how Ddd4jJavalinRuntime composes the auth, data, MQ, web, and cache providers.
• Deciding where a new module, sample, or test-support module belongs in the parent/BOM layering.
• Auditing cross-module guarantees such as Context/Subject/resource cleanup on success, exception, and async terminal states.

When NOT to Use

Do not use this skill when: