Skip to content

Ecosystem architecture and boundaries ​

This diagram describes repository and runtime responsibilities. It does not imply that every node is a stable release; check the catalog for status.

Verified boundaries ​

  • The five implementation repositories are currently private and under active restructuring; no public Maven artifact is advertised yet.
  • The local ddd4j baseline targets Java 17 and separates plain Java contracts from runtime-specific auto-configuration.
  • The module set covers aggregates, repositories, typed queries, domain events, CQRS, architecture rules, data, messaging, web, auth, and cache abstractions.

Suggested reading order ​

  1. Find the entry point closest to your use case in the diagram.
  2. Confirm whether the repository is public, a private preview, or archived.
  3. Open its README and confirm API, version, tests, and license.
  4. Run the smallest verification from Getting Started before business integration.

Last updated: