ddd4j-boot Web

Overview

Covers Spring MVC, WebFlux, Context, errors, authentication, Validation, idempotency, CORS, and Readiness uniformly, not split per artifact. Before use, confirm the maintenance line through ddd4j-boot-version-selection.

When to Use

• Choosing Spring MVC versus WebFlux for a ddd4j-boot service and assembling it from the ddd4j-web-webmvc / ddd4j-webflux modules.
• Unifying the error contract so domain and framework failures return one consistent response shape.
• Binding the ddd4j request Context (Subject, tenant) into the web request lifecycle — and releasing it on every exit path.
• Configuring validation, idempotency keys, CORS allowlists, and rate/concurrency limits through the boot web auto-configuration.
• Wiring readiness so it aggregates real dependency health instead of a hardcoded READY.
• Diagnosing web-layer issues on a specific Boot line (2.3–4.1): errors leaking stack traces, context not bound on async paths, or readiness reporting healthy while a dependency is down.

When NOT to Use

Do not use this skill when: