> ## Documentation Index > Fetch the complete documentation index at: https://docs.zeotap.com/llms.txt > Use this file to discover all available pages before exploring further. # Message Queue > A message refers to a piece of information that is processed by another system or it can be an actual payload, like files or metadata that trigger some processing in another sub-system. Queues help in processing these messages in order. A message queue is like a buffer that receives messages in a specific order and forwards them to the concerned sub-system or application in the same order. Message queues decouple the sender and recipient, allowing them to operate independently and at their own pace. Consumers retrieve messages from the queue when they are ready to process them. They can retrieve and process messages independently and at their own pace, allowing for asynchronous processing. ## Conventional vs. Pub/Sub Messaging Traditional messages are directly sent from a sender to a specific receiver. Here, the sender must know the receiver's address to deliver the message. This creates a tight coupling between the sender and receiver, making it difficult to dynamically scale the application or add new recipients. However, in pub/sub messaging senders (publishers) do not need to explicitly know the identity or location of the receivers (subscribers). Instead, publishers send messages to a topic or channel, and subscribers interested in receiving messages from that topic or channel can register themselves. The pub/sub system then delivers the message to all interested subscribers. ## Supported Message Queue Source Integrations The following are the Message Queue Source Integrations that Zeotap offers: