When.com Web Search

Search results

  1. Results From The WOW.Com Content Network
  2. RabbitMQ - Wikipedia

    en.wikipedia.org/wiki/RabbitMQ

    RabbitMQ is an open-source message-broker software (sometimes called message-oriented middleware) that originally implemented the Advanced Message Queuing Protocol (AMQP) and has since been extended with a plug-in architecture to support Streaming Text Oriented Messaging Protocol (STOMP), MQ Telemetry Transport (MQTT), and other protocols.

  3. Advanced Message Queuing Protocol - Wikipedia

    en.wikipedia.org/wiki/Advanced_Message_Queuing...

    AMQP is a binary application layer protocol, designed to efficiently support a wide variety of messaging applications and communication patterns. It provides flow controlled, [3] message-oriented communication with message-delivery guarantees such as at-most-once (where each message is delivered once or never), at-least-once (where each message is certain to be delivered, but may do so ...

  4. Message queue - Wikipedia

    en.wikipedia.org/wiki/Message_queue

    The message queue paradigm is a sibling of the publisher/subscriber pattern, and is typically one part of a larger message-oriented middleware system. Most messaging systems support both the publisher/subscriber and message queue models in their API, e.g. Java Message Service (JMS).

  5. Category:Message-oriented middleware - Wikipedia

    en.wikipedia.org/wiki/Category:Message-oriented...

    Main page; Contents; Current events; Random article; About Wikipedia; Contact us

  6. Message-oriented middleware - Wikipedia

    en.wikipedia.org/wiki/Message-oriented_middleware

    Messages stay in the queue until the time they are processed by a service consumer. Through the message queue, the application can be implemented independently - they do not need to know each other's position, or continue to implement procedures to remove the need for waiting to receive this message. [9]

  7. Message broker - Wikipedia

    en.wikipedia.org/wiki/Message_broker

    Message brokers are generally based on one of two fundamental architectures: hub-and-spoke and message bus. In the first, a central server acts as the mechanism that provides integration services, whereas with the latter, the message broker is a communication backbone or distributed service that acts on the bus . [ 3 ]

  8. MQTT - Wikipedia

    en.wikipedia.org/wiki/MQTT

    MQTT (originally an initialism of MQ Telemetry Transport [a]) is a lightweight, publish–subscribe, machine-to-machine network protocol for message queue/message queuing service. It is designed for connections with remote locations that have devices with resource constraints or limited network bandwidth, such as in the Internet of things (IoT).

  9. Publish–subscribe pattern - Wikipedia

    en.wikipedia.org/wiki/Publish–subscribe_pattern

    Publish–subscribe is a sibling of the message queue paradigm, and is typically one part of a larger message-oriented middleware system. Most messaging systems support both the pub/sub and message queue models in their API; e.g., Java Message Service (JMS).