Spring Kafka Event Integration

When to use

Invoke when a Spring Boot service must produce or consume Kafka events and the event contracts (topic names, message shape, idempotency keys, ordering expectations, delivery semantics) have been decided by backend-architecture. Use it for new producers and consumers, for reviewing an existing Kafka integration before production, or for adding the transactional outbox pattern.

Do not use for designing the event contract itself (use backend-architecture), for choosing the messaging substrate (use backend-architecture or system-design), for non-Kafka brokers, for broker or cluster provisioning (use infrastructure-platform and implementations/infrastructure/*), for in-process async (@Async, scheduling), or for the initial service scaffold (use spring-boot-service-scaffold).

Inputs

Required:

• Spring Boot service source tree (or scaffold output) targeting Kafka.
• Approved backend-architecture.md with event contracts: topic names, message shape, idempotency keys, ordering rule, delivery semantics, retry expectation, and DLQ policy.
• Broker connectivity details (bootstrap servers, security protocol) or the assumption that those land via configuration.

Optional: