ddd4j-cloud Data

Overview

Covers datasource, MyBatis, JPA, transactions, Seata, tenant, migration, and repository uniformly, not split per artifact. Choose the Cloud→Boot→ddd4j primary combination first, then read the current branch.

When to Use

• Selecting the access stack (datasource, MyBatis, JPA) for a ddd4j-cloud service and wiring repositories.
• Choosing between local transactions and Seata for cross-service work.
• Planning migration execution order and tenant-aware migration filtering.
• Wiring datasource lifecycle: owner, failure rollback, idempotent close.
• Verifying real database round-trips — transactions, tenant isolation, migration up/down.
• Diagnosing data-access failures that only appear with the real database in the loop.

When NOT to Use

Do not use this skill when: