messaging-brokers

Select messaging brokers and implement reliability patterns for distributed systems.

5|1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/roanbrasil/engineer-grade-agent-skills --skill messaging-brokers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: messaging-brokers
Source: https://github.com/roanbrasil/engineer-grade-agent-skills/tree/main/skills/messaging-brokers
Command: npx skills add https://github.com/roanbrasil/engineer-grade-agent-skills --skill messaging-brokers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common pain points of misselecting messaging infrastructure, implementing fragile messaging patterns, and facing data inconsistency from unsafe dual-write operations that lead to system outages and data loss in distributed systems.

Core Features & Use Cases

  • Multi-Broker Expertise: Covers RabbitMQ, Kafka, AWS SQS/SNS, Azure Service Bus, and NATS with selection criteria, primitive explanations, and configuration best practices for each.
  • Reliability Patterns: Provides implementation guidance for the outbox pattern, CDC, competing consumers, RPC over messaging, exponential backoff retries, and dead-letter queue strategies.
  • Anti-Pattern Mitigation: Identifies and corrects common topology and operational mistakes including queue sprawl, shared queue coupling, unbounded retries, and large message storage in brokers.
  • Real-World Use Case: For an e-commerce order processing system requiring exactly-once processing and strict per-user ordering, this Skill guides selection of AWS SQS FIFO queues, outbox pattern implementation to eliminate dual-write risks, and DLQ configuration with alerting for failed messages.

Quick Start

Use the messaging-brokers skill to select the optimal messaging broker for your use case, implement reliable outbox and retry patterns, and design a fault-tolerant broker topology for your distributed system.

Frequently Asked Questions about messaging-brokers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right message broker for distributed systems?

Choosing the right message broker requires evaluating throughput, latency, and ordering requirements for your workloads. This guidance compares RabbitMQ, Kafka, AWS SQS/SNS, Azure Service Bus, and NATS to match your specific event-driven architecture needs.

How do I implement the outbox pattern to prevent dual-write data inconsistency?

Implementing the outbox pattern prevents dual-write data inconsistency by storing messages in the same database transaction as your business data. This provides production-grade guidance for combining CDC with reliable event publishing in distributed systems.

What is the best way to configure dead-letter queues and idempotent consumers?

Configuring dead-letter queues and idempotent consumers ensures fault tolerance by capturing failed messages and preventing duplicate processing. This approach includes exponential backoff retries and alerting for operational reliability.

When should I use AWS SQS FIFO queues for e-commerce order processing?

AWS SQS FIFO queues are ideal for e-commerce order processing when you need exactly-once processing and strict per-user ordering. Combining them with the outbox pattern eliminates dual-write risks while maintaining message sequence integrity.

What are common message broker anti-patterns and how do I avoid them?

Common message broker anti-patterns include queue sprawl, shared queue coupling, unbounded retries, and storing large messages in brokers. Mitigating these topology and operational mistakes ensures stable inter-service communication and event streaming.