message-brokers

Implement RabbitMQ and Kafka messaging patterns for Python services.

1|1|Updated Mar 26, 2026

Search Tags:#asynchronous #kafka #pub/sub #rabbitmq #messaging-patterns #message-brokers

Ready to run

npx skills add https://github.com/PedroHBO/opencode-config-skills --skill message-brokers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: message-brokers
Source: https://github.com/PedroHBO/opencode-config-skills/tree/main/skills/message-brokers
Command: npx skills add https://github.com/PedroHBO/opencode-config-skills --skill message-brokers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The skill provides structured guidance and ready-to-use patterns for building reliable, asynchronous messaging systems using RabbitMQ and Kafka in Python, including pub/sub, dead-letter queues, event-driven architecture, and resilience patterns.

Core Features & Use Cases

Templates and code examples for producers and consumers across RabbitMQ and Kafka
Pub/sub messaging, DLQ strategies, retry patterns, and domain event design
Event-driven architectures with local dispatch and remote publishing

Quick Start

Activate this skill and follow the examples to connect a Python producer/consumer setup with RabbitMQ or Kafka.

Frequently Asked Questions about message-brokers

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

FAQPage Schema

How do I implement reliable messaging patterns for RabbitMQ and Kafka in Python?▼

To implement reliable messaging patterns for RabbitMQ and Kafka, you can use structured templates for producers and consumers that include connection management, retries, and dead-letter queues. These patterns enable asynchronous communication and event-driven architectures.

What is the best way to handle dead-letter queues and retries in asynchronous messaging?▼

The best way to handle dead-letter queues (DLQ) and retries in asynchronous messaging is by applying specific resilience patterns provided for RabbitMQ and Kafka. These strategies ensure failed messages are captured and reprocessed safely within your pub/sub workflows.

When do I need domain events and saga-style workflows in event-driven architectures?▼

You need domain events and saga-style workflows in event-driven architectures when coordinating complex cross-service transactions asynchronously. They provide clear usage guidance for managing distributed state and ensuring reliable remote publishing across microservices.

Does this messaging skill support both local dispatch and remote publishing for event-driven systems?▼

Yes, this messaging skill supports event-driven architectures with both local dispatch and remote publishing. It provides ready-to-use Python patterns for producers and consumers to handle domain events across RabbitMQ and Kafka clusters.

How do I set up a Python producer and consumer with RabbitMQ or Kafka?▼

You can set up a Python producer and consumer with RabbitMQ or Kafka by following ready-to-use code examples and templates. These examples cover connection management, pub/sub messaging, and domain event design to enable asynchronous communication.