ddd4j-boot Cache

Overview

Covers Caffeine/Guava/Hutool, Redis, Redisson, JetCache, TTL, CAS, and idempotency uniformly, not split per artifact. Before use, confirm the maintenance line through ddd4j-boot-version-selection.

When to Use

• Choosing among Caffeine/Guava/Hutool (local), Redis, Redisson, and JetCache for a ddd4j-boot service, matched to the consistency target.
• Wiring the cache auto-configuration so the domain's Cache SPI resolves to the assembled provider.
• Setting TTL units, capacity, and key strategy — and confirming the units actually mean what the configuration claims.
• Verifying atomic semantics the provider must prove: CAS compare-and-set contention and idempotency keys across instances.
• Overriding cache defaults with user beans or diagnosing why an unexpected cache bean is assembled.
• Diagnosing cache failures on a specific Boot line (2.3–4.1): beans present but Redis unreachable, TTL behaving differently than configured, invalidation not propagating.

When NOT to Use

Do not use this skill when: