YAML
Message Queue Systems - YAML
Message queue systems are middleware that enable asynchronous communication between distributed systems. Various systems exist with different characteristics such as high-throughput streaming processing, low-latency messaging, and cloud-native managed services. This list introduces major message queue systems including RabbitMQ, Apache Kafka, Amazon SQS, Redis, ActiveMQ, NATS, and Apache Pulsar.
message queue
distributed systems
asynchronous communication
middleware
event streaming
microservices
- code: "01"
slug: "rabbitmq"
name: "RabbitMQ"
description: "An open-source message broker with flexible routing capabilities."
type: "message-broker"
protocols:
- "AMQP"
- "MQTT"
- "STOMP"
throughput: "~1M messages/sec"
latency: "1-20ms"
persistence: true
messageReplay: false
cloudNative: false
deployment:
- "self-hosted"
- "cloud-managed"
- code: "02"
slug: "apache-kafka"
name: "Apache Kafka"
description: "A high-throughput distributed event streaming platform."
type: "event-streaming"
protocols:
- "Kafka Protocol"
throughput: "10M+ messages/sec"
latency: "2-10ms"
persistence: true
messageReplay: true
cloudNative: false
deployment:
- "self-hosted"
- "managed"
- code: "03"
slug: "amazon-sqs"
name: "Amazon SQS"
description: "A fully managed serverless message queue service provided by AWS."
type: "managed-queue"
protocols:
- "AWS API"
throughput: "~300K messages/sec"
latency: "10-100ms"
persistence: true
messageReplay: false
cloudNative: true
deployment:
- "managed"
- code: "04"
slug: "redis-streams"
name: "Redis Streams"
description: "Streaming capabilities provided by Redis, an in-memory data store."
type: "in-memory-stream"
protocols:
- "Redis Protocol"
throughput: "Very High"
latency: "Ultra Low"
persistence: "optional"
messageReplay: true
cloudNative: false
deployment:
- "self-hosted"
- "managed"
- code: "05"
slug: "apache-activemq"
name: "Apache ActiveMQ"
description: "A traditional JMS-based enterprise message broker."
type: "message-broker"
protocols:
- "JMS"
- "AMQP"
- "MQTT"
- "STOMP"
- "OpenWire"
throughput: "Medium"
latency: "Medium"
persistence: true
messageReplay: false
cloudNative: false
deployment:
- "self-hosted"
- code: "06"
slug: "nats"
name: "NATS"
description: "A cloud-native lightweight messaging system."
type: "cloud-native-messaging"
protocols:
- "NATS Protocol"
throughput: "Very High"
latency: "Ultra Low"
persistence: "optional"
messageReplay: true
cloudNative: true
deployment:
- "self-hosted"
- "managed"
- code: "07"
slug: "apache-pulsar"
name: "Apache Pulsar"
description: "A distributed messaging system with multi-tenancy and tiered storage."
type: "event-streaming"
protocols:
- "Pulsar Protocol"
throughput: "Very High"
latency: "Low"
persistence: true
messageReplay: true
cloudNative: true
deployment:
- "self-hosted"
- "managed"
- code: "08"
slug: "google-pubsub"
name: "Google Cloud Pub/Sub"
description: "A fully managed messaging service provided by Google Cloud."
type: "managed-queue"
protocols:
- "Google Cloud API"
throughput: "Very High"
latency: "Low"
persistence: true
messageReplay: true
cloudNative: true
deployment:
- "managed"
- code: "09"
slug: "azure-service-bus"
name: "Azure Service Bus"
description: "An enterprise integration messaging service provided by Microsoft Azure."
type: "managed-queue"
protocols:
- "AMQP"
- "HTTP/REST"
- "SBMP"
throughput: "High"
latency: "Low-Medium"
persistence: true
messageReplay: false
cloudNative: true
deployment:
- "managed"
- code: "10"
slug: "rocketmq"
name: "Apache RocketMQ"
description: "A highly available distributed messaging platform developed by Alibaba."
type: "message-broker"
protocols:
- "RocketMQ Protocol"
throughput: "Very High"
latency: "Low"
persistence: true
messageReplay: true
cloudNative: true
deployment:
- "self-hosted"
- "managed"