ddd4j-cloud Architecture

Overview

Covers parent, bom, dependencies, extensions, compatibility-tests, verification, samples, and upstream boundaries uniformly, not split per artifact. Choose the Cloud→Boot→ddd4j primary combination first, then read the current branch.

When to Use

• Reviewing the ddd4j-cloud module layout: parent, bom, dependencies, extensions, compatibility-tests, verification, samples.
• Deciding where a new extension belongs and which upstream Boot/ddd4j artifacts it may consume.
• Auditing extensions for canonical extensions naming with no old cmpt references.
• Reviewing upstream boundaries — what ddd4j-cloud consumes versus what it must not reimplement.
• Confirming at the architecture level that Context/Tenant restoration covers sync, async, Reactor, and Feign paths.
• Planning a read-only boundary review before a migration or fork merge.

When NOT to Use

Do not use this skill when: