event

What problem does it solve?

Helps teams design, validate, and harden event-driven systems to prevent schema breakage, duplicate processing, lost messages, and incorrect ordering so that services remain reliable and debuggable at scale.

Core Features & Use Cases

• Architecture Assessment: Detects brokers, schema files, outbox/CDC, and event-store patterns and classifies system maturity.
• Broker & Pattern Guidance: Recommends Kafka, RabbitMQ, SQS/SNS, or NATS based on throughput, ordering, and replay requirements and advises CQRS, sagas, or choreography where appropriate.
• Safety & Reliability Controls: Defines event envelope standards, schema versioning, DLQ and retry policies, idempotency patterns, outbox relay alternatives, snapshotting, and projection strategies.
• Use Case: Audit or migrate an orders-and-payments microservice to an event-driven architecture with minimal data loss, correct ordering, and replayability.

Quick Start

Ask the skill to assess the repository's event architecture for schema registry, DLQ configuration, retry/backoff policies, idempotent consumers, and recommended broker choice.