ddd4j Runtime

Overview

The runtime binds framework containers to the ddd4j core ports; core does not depend on any DI framework, and the runtime owns unique registration, request scope, and resource lifecycle.

When to Use

• Registering core SPIs — CommandBus, DomainEventPublisher, SubjectProvider, Cache, Repository — into Spring, Guice, Quarkus CDI, Micronaut, Vert.x, Helidon, or Dropwizard.
• Establishing Request/Thread/Reactive Context binding with restore on every terminal state.
• Designing startup ordering, dependency ordering between providers, and aggregated readiness.
• Handling partial startup failure: rolling back already-created resources in reverse order.
• Diagnosing duplicate registrations or missing entries behind Contexts / Registry / SubjectKit.
• Verifying runtime behavior with runtime-testkit plus the target framework's own tests.

When NOT to Use

Do not use this skill when: