ddd4j-quarkus Cache

Overview

Covers Quarkus Cache, Redis, the ddd4j Cache SPI, TTL, CAS, idempotency, and CDI scope uniformly, not split per artifact. Choose 3.3.x or 4.0.x first, then read the current source.

When to Use

• Choosing among Quarkus Cache, Redis, and the ddd4j Cache SPI against the service's consistency target.
• Using shared CAS for multi-instance idempotency (replay protection across replicas).
• Registering cache providers with correct CDI scopes and configuration mappings.
• Owning cache connection lifecycle: startup/shutdown observers and idempotent close.
• Testing TTL, invalidate, concurrency, and real CAS contention with QuarkusTest.
• Reviewing existing cache wiring — scopes, eviction versus idempotency keys, native compatibility — on the 3.3.x or 4.0.x line.

When NOT to Use

Do not use this skill when: