ddd4j Core

Overview

Guide domain modeling and framework-agnostic code against the current io.ddd4j.core public contracts. The core boundary is: ddd4j-core defines DDD / CQRS / SPI; Spring, Guice, Quarkus, Javalin, MyBatis, and friends only assemble in the adapter layer.

When to Use

• Modeling or reviewing a ddd4j domain aggregate (AggregateRoot<ID>) in Active Record or Event Sourcing mode.
• Implementing the write side — Command, CommandExecutor, CommandBus, Result<R>.
• Implementing the read side — Query<M>, PersistenceQueryScope<M, P>, Repository<M, ID>.
• Working with DomainEvent<ID> metadata, publication, or replay.
• Deciding whether a dependency belongs in the domain or in the adapter layer.
• Resolving Contexts, ThreadContext, Subject, or Cache SPI contracts.

When NOT to Use

Do not use this skill when: