event-driven-architecture-expert

What problem does it solve?

This Skill helps teams design and operate reliable asynchronous messaging systems that prevent data loss, preserve ordering where required, and provide operational controls for retries, dead-letter handling, and schema evolution.

Core Features & Use Cases

• Broker selection & topology: guidance for choosing Kafka, RabbitMQ, Redis Streams, or cloud event buses and designing topics/exchanges, partitions, and routing.
• Reliability patterns: transactional outbox, idempotent consumers, retry strategies, dead-letter queues, and partitioning for ordered processing.
• Schema & serialization: CloudEvents recommendations, Avro/Protobuf/JSON Schema guidance, and schema registry best practices for backward compatibility.
• Operational playbook: consumer lag monitoring, queue-depth alerting, load testing at 2x expected throughput, and recovery procedures for crashed agents.
• Use case: Build a decoupled order-processing pipeline where transactions write to an outbox, a publisher forwards events to Kafka, and multiple consumers (fulfillment, notifications, analytics) process events with DLQ routing on repeated failures.

Quick Start

Use the event-driven architecture expert to design a Kafka-based ordering pipeline with transactional outbox, idempotent consumers, and dead-letter queue policies.