streaming-event-architect

What problem does it solve?

This Skill helps design the internal event and streaming backbone between services so teams can avoid duplicate processing, out-of-order updates, dead-letter black holes, and unclear delivery guarantees.

Core Features & Use Cases

• Flow Classification: Separates internal notifications, state-transfer events, and commands before choosing streams or queues.
• Delivery Semantics: Defines honest at-least-once behavior with explicit idempotency, retry policy, dead-letter ownership, and replay procedures.
• Ordering and Partitioning: Sets partition keys and ordering scope clearly, including skew and tenant hot-key risk.
• CDC and Schema Rules: Designs change data capture ingestion, retention versus compaction, and schema compatibility rules for internal consumers.
• Use Case: A platform team can use this Skill when rebuilding an event bus, fixing duplicate payment events, or adding CDC from a transactional database into internal streams.

Quick Start

Ask for an internal streaming design for your services, including flow classification, partition keys, delivery semantics, retry and DLQ handling, replay rules, and CDC ingestion if needed.