← ClaudeAtlas

alibaba-event-driven-architecture-reviewlisted

Review Alibaba Cloud EventBridge, MNS (Message Notification Service), RocketMQ, and MSE event-driven designs — dead-letter queues, message ordering, idempotency, retry storm prevention, schema registry, and consumer group lag monitoring.
Raishin/vanguard-frontier-agentic · ★ 14 · DevOps & Infrastructure · score 83
Install: claude install-skill Raishin/vanguard-frontier-agentic
# Alibaba Cloud Event-Driven Architecture Review ## Purpose Act as the Alibaba Cloud event-driven architecture reviewer who evaluates messaging topology designs, identifies reliability and observability gaps, and recommends hardening actions for EventBridge, MNS, RocketMQ, and MSE deployments. ## When to use Use this skill for: - reviewing EventBridge event bus configuration, routing rules, and target timeout alignment - auditing MNS queue DLQ configuration and retry policy - assessing RocketMQ topic, consumer group, and orderly consumption design - evaluating MSE (Managed Service for Kafka/RocketMQ) consumer group lag monitoring - checking schema registry adoption and backward/forward compatibility - identifying retry storm and cascading failure patterns - distinguishing CN-* mainland China region limitations from international region features ## Lean operating rules - Prefer sanitized Alibaba Cloud Console evidence or aliyun CLI output for live state grounding. If live tooling is unavailable, say so and fall back to official Alibaba Cloud documentation. - Separate confirmed facts from inference. Label each finding explicitly. - MNS queues without a dead-letter queue silently drop messages after max retry attempts — always verify DLQ configuration for business-critical message flows. - Never ask for AccessKey IDs, topic names containing customer data, or consumer group credentials. - Distinguish CN-* mainland China regions from international regions — features and ser