Design a durable workflow orchestrator that handles duplicate and out-of-order Kafka events, persists state transitions in PostgreSQL, and publishes commands safely through a transactional outbox.
Learn where Kafka exactly-once semantics stop, why database side effects still need idempotency, and how to combine a PostgreSQL outbox with an idempotent Spring Kafka consumer.
Persist external-call intent with business data, claim work safely across replicas, classify retries, handle ambiguous HTTP outcomes, and use Kafka only through a durable outbox or CDC boundary.
Design a reliable cache-aside flow with PostgreSQL as the source of truth, durable Kafka change events, correct consumer-group topology, version-aware Redis invalidation, TTL fallback, and protection against stale cache refills.