implement-eda

Orchestrate event-driven communication across Kafka, RabbitMQ, and in-memory channels.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fireflyframework/fireflyframework-claude-skills --skill implement-eda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-eda
Source: https://github.com/fireflyframework/fireflyframework-claude-skills/tree/main/skills/implement-eda
Command: npx skills add https://github.com/fireflyframework/fireflyframework-claude-skills --skill implement-eda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates implementing event-driven architecture in Firefly Framework services by providing unified abstractions for publishing and consuming events across Kafka, RabbitMQ, or in-memory Spring events, decoupling business logic from transport details.

Core Features & Use Cases

  • Unified event publishing and consumption APIs across multiple transports (Kafka, RabbitMQ, APPLICATION_EVENT).
  • Declarative and programmatic publishing/consumption with support for DLQ, retries, and circuit breakers.
  • CQRS integration via automatic domain-event publication and diverse serialization options (JSON, Avro, Protobuf).
  • Dynamic listener registration and global event filtering for scalable, resilient event-driven architectures.

Quick Start

Publish a sample OrderCreatedEvent to the order-events channel to verify end-to-end publishing.

Frequently Asked Questions about implement-eda

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement event-driven architecture across Kafka and RabbitMQ without coupling business logic to the transport layer?▼

You can implement event-driven architecture using unified abstractions for publishing and consuming events across Kafka, RabbitMQ, and in-memory Spring events, which decouples business logic from underlying transport details.

Can I use CQRS with domain events in a Spring Boot application?▼

Yes, CQRS integration is supported by automatically publishing domain events and providing declarative consumption, allowing Spring Boot services to react to inbound events seamlessly.

What serialization formats are supported for event-driven communication?▼

Event-driven communication supports pluggable serializers including JSON, Avro, and Protobuf, enabling flexible and diverse serialization options for publishing domain events.

How do I build resilient event listeners with retries and circuit breakers?▼

Resilient event listeners are built using built-in support for dead-letter queues (DLQ), retries, and circuit breakers, alongside dynamic listener registration and global event filtering.

What's the best way to publish a domain event to verify end-to-end event-driven services?▼

The best way to verify end-to-end event-driven services is by declaratively or programmatically publishing a sample event, such as an OrderCreatedEvent, to a designated channel.