using-message-queues

Implement asynchronous communication patterns with Kafka, RabbitMQ, NATS, and Redis Streams.

503|73|Updated Nov 13, 2025

Search Tags:#event-driven #kafka #temporal #celery #rabbitmq #message queues #async communication

Ready to run

npx skills add https://github.com/ancoleman/ai-design-components --skill using-message-queues

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: using-message-queues
Source: https://github.com/ancoleman/ai-design-components/tree/main/skills/using-message-queues
Command: npx skills add https://github.com/ancoleman/ai-design-components --skill using-message-queues

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides patterns and tools for implementing asynchronous communication, enabling you to build resilient, scalable, and decoupled applications.

Core Features & Use Cases

Asynchronous Communication: Decouple services and handle long-running operations without blocking.
Event-Driven Architectures: Build systems that react to events in real-time.
Background Job Processing: Offload time-consuming tasks to background workers.
Use Case: Process large video files asynchronously by sending a message to a queue, having a worker pick it up, process it, and then notify the user upon completion.

Quick Start

Use the using-message-queues skill to implement a Kafka producer that sends order creation events.

Frequently Asked Questions about using-message-queues

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

FAQPage Schema

How do I decouple services using message queues for event-driven architecture?▼

Message queues decouple services by enabling asynchronous communication, allowing producers to send events to a broker like Kafka or RabbitMQ without waiting for consumers to process them. This builds resilient, scalable event-driven systems.

What's the best way to process background jobs asynchronously?▼

Background job processing offloads time-consuming tasks to dedicated workers using task queues like Celery or BullMQ. A service sends a message to the queue, and a worker picks it up, processes it, and notifies the user upon completion.

When should I use Temporal versus Celery for workflow orchestration?▼

Use Temporal for complex workflow orchestration and durable state management across distributed services, whereas Celery is better suited for simple background task queuing and asynchronous job execution within a single application.

How do I implement a Kafka producer for event streaming?▼

To implement a Kafka producer for event streaming, you configure your application to send order creation events to a Kafka topic. This enables real-time event-driven reactions by decoupling the event generation from downstream consumers.

Does this event-driven approach support Redis Streams and NATS?▼

Yes, this asynchronous communication approach supports multiple message brokers including NATS and Redis Streams, alongside Kafka and RabbitMQ, providing flexible options for event streaming and service decoupling.

Why does asynchronous communication fail to handle long-running operations without blocking?▼

Asynchronous communication fails to block long-running operations by design, as it offloads the task to a background worker via a message queue. The original service continues processing other requests, ensuring the system remains responsive.