skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
rrezartprebreza/spring-boot-skills70 installs

event-driven-messaging

Use when implementing Kafka, RabbitMQ, Pulsar, or JMS producers and consumers in Spring Boot 3. Covers event contracts, idempotency, retries, dead-letter handling, ordering, and outbox delivery.

How do I install this agent skill?

npx skills add https://github.com/rrezartprebreza/spring-boot-skills --skill event-driven-messaging
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides architectural guidance and code examples for building event-driven systems in Spring Boot 4. It promotes industry-standard best practices such as idempotency, transactional outbox patterns, and dead-letter queues. No malicious patterns, obfuscation, or unauthorized data access were detected.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Event-Driven Messaging

Design for at-least-once delivery unless the complete system proves stronger semantics.

Event contract

  • Use an immutable event envelope with eventId, eventType, occurredAt, schemaVersion, and payload.
  • Treat published schemas as APIs. Add fields compatibly and never silently change meaning.
  • Put correlation and causation IDs in headers or the envelope.
  • Do not publish JPA entities or framework-specific serialization shapes.

Producer rules

  • Publish only after the originating state change is durable.
  • Use a transactional outbox when database state and broker publication must agree.
  • Use deterministic partition keys when per-aggregate ordering matters.
  • Configure delivery timeout and acknowledgements explicitly.

Consumer rules

  • Make handlers idempotent with a durable processed-event record or naturally idempotent write.
  • Keep the transaction boundary around the state change and idempotency marker.
  • Classify transient and permanent failures before configuring retries.
  • Bound retries with backoff, then route poison messages to a dead-letter destination.
  • Preserve the original event, failure reason, and attempt count for replay.

Testing

  • Test serialization compatibility and handler idempotency.
  • Use Testcontainers for broker integration tests.
  • Test duplicate, reordered, delayed, and poison messages.

Examples

  • See examples/good-consumer.java and examples/bad-consumer.java.

Verification scope

The workflow fixture compiles good-consumer.java directly and checks duplicate delivery, concurrent invocation and claim/effect rollback against PostgreSQL. It calls the consumer directly: broker serialization, listener wiring, offsets, retries and dead-letter delivery are not covered. See the coverage matrix for pinned versions and remaining gaps.

Gotchas

  • Agent assumes exactly-once delivery because the broker supports transactions - end-to-end side effects still need idempotency.
  • Agent retries validation failures forever - dead-letter permanent failures promptly.
  • Agent publishes inside a database transaction without an outbox - a crash can split state and event delivery.
  • Agent uses a random partition key - ordering for one aggregate is then lost.
  • Agent deserializes directly into a JPA entity - use a versioned event contract.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/rrezartprebreza/spring-boot-skills/event-driven-messaging">View event-driven-messaging on skillZs</a>