alibaba-event-driven-architecture-review

Name: alibaba-event-driven-architecture-review
Author: Raishin

17stars3forks

How to install alibaba-event-driven-architecture-review?

raishin/vanguard-frontier-agentic/alibaba-event-driven-architecture-review

$npx -y skills add Raishin/vanguard-frontier-agentic --skill alibaba-event-driven-architecture-review

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# Alibaba Cloud Event-Driven Architecture Review
2
3	## Purpose
4
5	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.
6
7	## When to use
8
9	Use this skill for:
10
11	- reviewing EventBridge event bus configuration, routing rules, and target timeout alignment
12	- auditing MNS queue DLQ configuration and retry policy
13	- assessing RocketMQ topic, consumer group, and orderly consumption design
14	- evaluating MSE (Managed Service for Kafka/RocketMQ) consumer group lag monitoring
15	- checking schema registry adoption and backward/forward compatibility
16	- identifying retry storm and cascading failure patterns
17	- distinguishing CN-* mainland China region limitations from international region features
18
19	## Lean operating rules
20
21	- 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.
22	- Separate confirmed facts from inference. Label each finding explicitly.
23	- MNS queues without a dead-letter queue silently drop messages after max retry attempts — always verify DLQ configuration for business-critical message flows.
24	- Never ask for AccessKey IDs, topic names containing customer data, or consumer group credentials.
25	- Distinguish CN-* mainland China regions from international regions — features and service limits differ and cannot be assumed to be equivalent.
26
27	## Key event-driven guidance
28
29	- MNS (Message Notification Service): queue-based pull model; without a DLQ, messages are dropped after `MaxReceiveCount` retries; always configure DLQ for business-critical flows.
30	- RocketMQ (ApsaraMQ): supports orderly and concurrent consumption; orderly consumption guarantees per-queue ordering but requires single-threaded consumers per queue — multi-threaded orderly consumers will lose ordering guarantees.
31	- EventBridge: push model to FC3, API Gateway, MNS, and more; push timeout is 600 seconds per invocation; target must respond within that window or the event is dropped; retry policy applies to failed pushes only, not timeouts.
32	- MSE Kafka: consumer group rebalance storms occur during rolling deployments when `session.timeout.ms` is too short relative to restart duration — tune `max.poll.interval.ms` and `session.timeout.ms` together.
33	- Consumer lag: consumer group lag is the leading indicator of consumer failure in both RocketMQ and MSE Kafka — CloudMonitor alerts on lag must be configured for all production consumer groups.
34	- Schema registry: EventBridge schema registry enables event schema discovery and code generation; without it, producer schema changes silently break consumers.
35
36	## References
37
38	Load these only when needed:
39
40	- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full event-driven architecture review or formatting the final assessment output.
41	- [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud service behavior or product feature claims.
42
43	## Response minimum
44
45	Return, at minimum:
46
47	- the event flow topology and service selection assessment,
48	- dead-letter queue and retry configuration for each messaging service,
49	- message ordering and idempotency posture,
50	- consumer capacity and lag monitoring coverage,
51	- schema evolution and compatibility risks,
52	- retry storm and cascading failure risks,
53	- prioritized hardening recommendations.

People who liked this also viewed

6 picks

Type

alibaba-event-driven-architecture-review

17stars3forks

View on GitHub

How to install alibaba-event-driven-architecture-review?

raishin/vanguard-frontier-agentic/alibaba-event-driven-architecture-review

$npx -y skills add Raishin/vanguard-frontier-agentic --skill alibaba-event-driven-architecture-review

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Alibaba Cloud Event-Driven Architecture Review
2
3	## Purpose
4
5	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.
6
7	## When to use
8
9	Use this skill for:
10
11	- reviewing EventBridge event bus configuration, routing rules, and target timeout alignment
12	- auditing MNS queue DLQ configuration and retry policy
13	- assessing RocketMQ topic, consumer group, and orderly consumption design
14	- evaluating MSE (Managed Service for Kafka/RocketMQ) consumer group lag monitoring
15	- checking schema registry adoption and backward/forward compatibility
16	- identifying retry storm and cascading failure patterns
17	- distinguishing CN-* mainland China region limitations from international region features
18
19	## Lean operating rules
20
21	- 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.
22	- Separate confirmed facts from inference. Label each finding explicitly.
23	- MNS queues without a dead-letter queue silently drop messages after max retry attempts — always verify DLQ configuration for business-critical message flows.
24	- Never ask for AccessKey IDs, topic names containing customer data, or consumer group credentials.
25	- Distinguish CN-* mainland China regions from international regions — features and service limits differ and cannot be assumed to be equivalent.
26
27	## Key event-driven guidance
28
29	- MNS (Message Notification Service): queue-based pull model; without a DLQ, messages are dropped after `MaxReceiveCount` retries; always configure DLQ for business-critical flows.
30	- RocketMQ (ApsaraMQ): supports orderly and concurrent consumption; orderly consumption guarantees per-queue ordering but requires single-threaded consumers per queue — multi-threaded orderly consumers will lose ordering guarantees.
31	- EventBridge: push model to FC3, API Gateway, MNS, and more; push timeout is 600 seconds per invocation; target must respond within that window or the event is dropped; retry policy applies to failed pushes only, not timeouts.
32	- MSE Kafka: consumer group rebalance storms occur during rolling deployments when `session.timeout.ms` is too short relative to restart duration — tune `max.poll.interval.ms` and `session.timeout.ms` together.
33	- Consumer lag: consumer group lag is the leading indicator of consumer failure in both RocketMQ and MSE Kafka — CloudMonitor alerts on lag must be configured for all production consumer groups.
34	- Schema registry: EventBridge schema registry enables event schema discovery and code generation; without it, producer schema changes silently break consumers.
35
36	## References
37
38	Load these only when needed:
39
40	- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full event-driven architecture review or formatting the final assessment output.
41	- [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud service behavior or product feature claims.
42
43	## Response minimum
44
45	Return, at minimum:
46
47	- the event flow topology and service selection assessment,
48	- dead-letter queue and retry configuration for each messaging service,
49	- message ordering and idempotency posture,
50	- consumer capacity and lag monitoring coverage,
51	- schema evolution and compatibility risks,
52	- retry storm and cascading failure risks,
53	- prioritized hardening recommendations.

People who liked this also viewed

6 picks

Type