Messaging terms
Decoupling systems through reliable, async communication
Asynchronous messaging decouples producers from consumers and makes distributed systems more resilient. This category covers message queues, pub/sub patterns, event streaming with Kafka, delivery guarantees, dead letter queues, and the architecture patterns that make event-driven systems robust at scale. When you need services to communicate without depending on each other's availability, messaging is the answer.
More on Messaging
History
Messaging emerged as a critical architectural pattern in distributed systems during the 1980s and 1990s, when enterprises needed reliable asynchronous communication between decoupled applications. Early message-oriented middleware (MOM) systems like IBM MQ and TIBCO enabled guaranteed delivery and decoupling, becoming foundational for enterprise integration. The rise of internet-scale applications in the 2000s drove demand for higher-throughput, distributed messaging systems, leading to open-source platforms like RabbitMQ (2007) and Apache Kafka (2011), which fundamentally changed how organizations handle event streams and real-time data. Modern messaging practice has evolved to encompass diverse patterns—pub/sub, event sourcing, CQRS, and saga patterns—addressing challenges in microservices architectures, distributed transactions, and asynchronous workflows. Today, messaging is essential infrastructure for cloud-native systems, event-driven architectures, and real-time data processing pipelines.
Key concepts
- Message Queue
- Message Broker
- Pub/Sub Pattern
- Message Ordering Guarantees
- At-Least-Once Delivery
- Consumer Groups
- Message Idempotency
- CQRS Pattern
Best references
-
Apache Kafka Documentation Official reference for Kafka architecture, APIs, and operational concepts. Essential for understanding partitions, consumer groups, delivery semantics, and replication.
-
RabbitMQ Official Documentation Authoritative guide to RabbitMQ messaging patterns, exchanges, queues, and reliability features. Core resource for understanding traditional message broker design.
-
Enterprise Integration Patterns by Gregor Hohpe & Bobby Woolf Seminal reference covering message queues, pub/sub, routing, transformation, and other foundational patterns. The canonical taxonomy for messaging system design.
-
Protocol Buffers Documentation Official specification for Protocol Buffers serialization format. Essential for understanding modern message serialization alongside Avro.
-
CQRS and Event Sourcing by Microsoft Authoritative explanation of CQRS pattern and its relationship to event-driven messaging architectures, with practical examples and trade-offs.
-
The Saga Pattern (Chris Richardson) Definitive resource on the Saga pattern for distributed transactions using messaging, distinguishing choreography and orchestration approaches.
✦ Latest in Messaging
Typed relationships here
Edges touching a Messaging term.
- GraphQL Subscriptions Realizes Pub/Sub Pattern Sep 25
- Message Queue Realizes At-Least-Once Delivery Sep 14
- Message Broker Contains Message Queue Sep 10
- Transactional Outbox Pattern Enables Exactly-Once Delivery Aug 11
- Apache Kafka Fundamentals Often seen in CQRS Pattern Aug 8
Exactly-once delivery connects to domain events through the outbox pattern, which atomically writes those events to a database table in the same transaction as the business data that produced them. The pattern is what carries the events safely to the broker without loss or duplication, so the delivery guarantee is meaningfully about the domain events being relayed — remove the outbox and there's no mechanism tying the messaging guarantee to the architectural event records. That atomic write is the load-bearing piece: it's the bridge between 'something happened in the domain' and 'the broker delivers it exactly once'.
🤖 AI Guestbook — Messaging educational data only
|
|
Last 30 days
Agents 13
Google 6Amazonbot 3PetalBot 3SEMrush 1
PetalBot 1Google 1
Amazonbot 476PetalBot 369Google 269SEMrush 267Ahrefs 255Perplexity 250Scrapy 210Bing 154ChatGPT 142Unknown AI 86Claude 83Applebot 66Twitter/X 62Baidu 44Brave Search 41Meta AI 36Majestic 24Common Crawl 19Sogou 8Qwen 3You.com 3DuckDuckGo 2
Most referenced — Messaging
How they use it
crawler 2.7k
crawler_json 106
your_contextpost 3
your_context 1
pre-tracking 19
Category total2.9k pings
Terms pinged29 / 29
Distinct agents21
Apache Kafka Concepts
1
Kafka is a distributed log — producers append to immutable, ordered topics partitioned for parallelism, consumers read at their own pace and replay from any offset.
7mo ago
Messaging intermediate
Apache Kafka Fundamentals
PHP 7.0+
8
A distributed event streaming platform that stores messages as an immutable ordered log partitioned across a cluster — optimised for high-throughput, durable, replayable event streams rather than traditional task queues.
7mo ago
Messaging advanced
At-Least-Once Delivery
3
At-least-once delivery guarantees a message is delivered to at least one consumer, possibly multiple times — consumers must be idempotent to handle duplicates safely.
7mo ago
Messaging intermediate
Backpressure
Backpressure signals upstream producers to slow down when downstream consumers can't keep up — preventing queue overflow, memory exhaustion, and system collapse under load.
7mo ago
Messaging intermediate
Consumer Groups
1
Consumer groups allow multiple consumers to process messages from a topic in parallel — each partition assigned to one consumer, enabling horizontal scaling without duplicate processing.
7mo ago
Messaging intermediate
CQRS Pattern
PHP 7.0+
1
Command Query Responsibility Segregation — separating the write model (commands that change state) from the read model (queries that return data), allowing each to be optimised independently.
7mo ago
Messaging advanced
Dead Letter Queue
1
A Dead Letter Queue (DLQ) captures messages that can't be processed — expired, malformed, or repeatedly failed — enabling later inspection and replay without losing data.
7mo ago
Messaging intermediate
Event Sourcing vs Messaging
2
Event sourcing stores all state changes as immutable events (the source of truth) — messaging delivers events between services. They complement each other but serve different purposes.
7mo ago
Messaging intermediate
Exactly-Once Delivery
5
Exactly-once delivery ensures each message is processed exactly once — achievable only with coordination between broker and consumer using transactions or idempotent producers.
7mo ago
Messaging advanced
Message Broker
3
A message broker is middleware that receives, routes, and delivers messages between producers and consumers — decoupling services and enabling async communication at scale.
7mo ago
Messaging intermediate
Message Idempotency
1
An idempotent message handler produces the same result whether called once or many times — essential for at-least-once delivery where duplicates are expected.
7mo ago
Messaging intermediate
Message Ordering Guarantees
3
Message ordering is only guaranteed within a single Kafka partition or RabbitMQ queue — multiple partitions or consumers break FIFO order across the full topic.
7mo ago
Messaging intermediate
Message Queue
5
A durable buffer that decouples the component producing work (producer) from the component processing it (consumer), enabling async processing, load levelling, and retry logic without direct coupling.
7mo ago
Messaging intermediate
Message Queue Patterns
Core messaging patterns — competing consumers, scatter-gather, request-reply, message filter, and routing slip — solve recurring distributed communication challenges.
7mo ago
Messaging intermediate
Message Serialization (Avro/Protobuf)
Binary serialization formats (Avro, Protobuf, MessagePack) are faster and smaller than JSON for high-throughput messaging — with schema evolution support for Avro.
7mo ago
Messaging intermediate
Pub/Sub Pattern
3
Pub/Sub (Publish-Subscribe) decouples senders from receivers — publishers emit events to topics, all interested subscribers receive them without knowing each other.
7mo ago
Messaging beginner
RabbitMQ Concepts
RabbitMQ is an AMQP message broker with flexible routing via exchanges — direct, topic, fanout, and headers routing enables complex message dispatch patterns.
7mo ago
Messaging intermediate
RabbitMQ Fundamentals
PHP 7.0+
A message broker implementing the AMQP protocol — producers publish to exchanges, exchanges route messages to queues via bindings, and consumers pull from queues — providing flexible routing, acknowledgements, and dead-letter handling.
7mo ago
Messaging intermediate
Saga Pattern
1
The Saga pattern manages distributed transactions across services using a sequence of local transactions — each step publishes an event, and compensating transactions undo completed steps on failure.
7mo ago
Messaging advanced
Topics & Partitions
1
Kafka topics are divided into partitions — the unit of parallelism and ordering. More partitions = more parallelism; partition key determines which partition a record lands in.
7mo ago
Messaging intermediate