message-broker-selection

Evaluate workload requirements to select log-based or queue-based messaging brokers.

1|Updated Jun 20, 2026

Search Tags:#messaging #design #architecture #kafka #broker #rabbitmq

Ready to run

npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill message-broker-selection-shafibabar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: message-broker-selection
Source: https://github.com/shafibabar/SDLC-Artifact-Factory/tree/main/skills/message-broker-selection
Command: npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill message-broker-selection-shafibabar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves the common architectural error of treating log-based and queue-based brokers as interchangeable, preventing production failures caused by choosing the wrong messaging model for a specific workload.

Core Features & Use Cases

Selection Framework: Provides a clear decision axis based on replay, retention, and ordering requirements.
Model Comparison: Offers a deep-dive contrast between log-based (Redpanda/Kafka) and queue-based (RabbitMQ/AMQP) architectures.
Use Case: Use this skill when designing a new service to determine if your messaging needs require the immutable history of a log or the transient task-dispatch capabilities of a queue.

Quick Start

Analyze the current messaging workload requirements and apply the replay question to determine whether to use a log-based or queue-based broker.

Frequently Asked Questions about message-broker-selection

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

FAQPage Schema

How do I choose between Kafka and RabbitMQ for my messaging architecture?▼

Choosing between Kafka and RabbitMQ requires evaluating workload criteria like replay, retention, and ordering to determine if a log-based or queue-based broker fits your domain event patterns.

What is the difference between log-based and queue-based messaging brokers?▼

Log-based brokers provide immutable history retention for event streams, while queue-based brokers handle transient task-dispatch patterns, preventing the architectural anti-pattern of treating both models as swappable.

When do I need a log-based broker instead of a queue-based broker?▼

You need a log-based broker when your messaging workload demands replay capabilities and strict retention for domain events, rather than the transient task-dispatch capabilities of a queue.

How do I evaluate messaging workload requirements for system design?▼

Evaluate messaging workload requirements by applying replay, retention, and ordering questions to justify your infrastructure selection, explicitly aligning messaging models with domain event or task-dispatch patterns.

Why does treating Kafka and RabbitMQ as interchangeable cause production failures?▼

Treating log-based and queue-based brokers as interchangeable causes production failures because workloads requiring immutable event history fail when deployed on transient task-dispatch queue architectures.

Can I use a queue-based broker for event replay and retention requirements?▼

Queue-based brokers lack the immutable history retention required for event replay, meaning you must select a log-based architecture to satisfy workloads with strict replay and retention criteria.