ddd4j-boot Data

Overview

Covers JDBC, JPA, MyBatis, MyBatis-Plus, Flyway, transactions, Repository, Projection, and Outbox uniformly, not split per artifact. Before use, confirm the maintenance line through ddd4j-boot-version-selection.

When to Use

• Choosing among JDBC, JPA, MyBatis, and MyBatis-Plus for a ddd4j-boot service and assembling it through the boot data auto-configuration.
• Registering the concrete Repository implementation that the domain's Repository SPI expects.
• Wiring transactions and the transaction manager around aggregate persistence, Projections, and the Outbox.
• Setting up Flyway migrations, including verifying up/down against a real database.
• Overriding data defaults with user beans, or checking why an assembled data bean is not the implementation you expected.
• Diagnosing data-access failures on a specific Boot line (2.3–4.1): wiring present but round-trips failing, transactions not rolling back, Outbox not dispatching.

When NOT to Use

Do not use this skill when: