Advanced Message Queuing Protocol

Summary

The Advanced Message Queuing Protocol (AMQP) is an open standard application layer protocol for message-oriented middleware. The defining features of AMQP are message orientation, queuing, routing (including point-to-point and publish-and-subscribe), reliability and security. AMQP mandates the behavior of the messaging provider and client to the extent that implementations from different vendors are interoperable, in the same way as SMTP, HTTP, FTP, etc. have created interoperable systems. Previous standardizations of middleware have happened at the API level (e.g. JMS) and were focused on standardizing programmer interaction with different middleware implementations, rather than on providing interoperability between multiple implementations. Unlike JMS, which defines an API and a set of behaviors that a messaging implementation must provide, AMQP is a wire-level protocol. A wire-level protocol is a description of the format of the data that is sent across the network as a stream of

Official source

https://en.wikipedia.org/wiki/Advanced_Message_Queuing_Protocol

About this result

This page is automatically generated and may contain information that is not correct, complete, up-to-date, or relevant to your search query. The same applies to every other page on this website. Please make sure to verify the information with EPFL's official sources.

Related publications (4)

Related publications

Related people

Related units

Related concepts (6)

Related concepts

Related courses (1)

Related courses

Related lectures (1)

Related lectures

Real-Time Control of Microgrids with Explicit Power Setpoints: an API for Resource Agents

Andrey Bernstein, Niek Johannes Bouman, Jean-Yves Le Boudec

Renewable energy resources, such as photovoltaic panels, typically have very volatile power-injection characteristics, which poses a number of challenges to the real-time control of electrical grids that contain a significant fraction of these resources. Recently, a new paradigm for controlling such grids, termed COMMELEC, was proposed; it uses explicit power setpoints instead of droop-control. Central to this new paradigm is an abstract message format that enables resources to delegate the decisions related to their control actions to a grid controller. This is essential to the feasibility of the approach, as it makes the grid controller device-independent. However, it leaves to the resource agents the burden of translating device-specific information into this abstract format. In this paper, we present a solution to this problem; more specifically, we present a very simple Application Programming Interface (API) that can be used to design a COMMELEC-compliant resource agent. We present an easy-to-use High-Level API, which supports a pre- defined set of resources, such as a battery or a photovoltaic panel. We also describe a Low-Level API that provides full access to the underlying message format, and allows to design a resource agent that is not supported by the High-Level API. For message serialization, we use the Cap’n Proto framework, which allows for efficient manipulations of the mathematical objects used in COMMELEC.

2015

Users often wish to participate in online groups anonymously, but misbehaving users may abuse this anonymity to disrupt the group. Messaging protocols such as Mix-nets and DC-nets leave online groups vulnerable to denial-of-service and Sybil attacks, while accountable voting protocols are unusable or inefficient for general anonymous messaging. We present the first general messaging protocol that offers provable anonymity with accountability for moderate-size groups, and efficiently handles unbalanced loads where few members have much data to transmit in a given round. The N group members first cooperatively shuffle an N x N matrix of pseudorandom seeds, then use these seeds in N "pre-planned" DC-nets protocol runs. Each DC-nets run transmits the variable-length bulk data comprising one member's message, using the minimum number of bits required for anonymity under our attack model. The protocol preserves message integrity and one-to-one correspondence between members and messages, makes denial-of-service attacks by members traceable to the culprit, and efficiently handles large and unbalanced message loads. A working prototype demonstrates the protocol's practicality for anonymous messaging in groups of 40+ member nodes.

2010

ProtoPeer: from Simulation to Live Deployment in One Step

Karl Aberer, Zoran Despotovic, Wojciech Galuba

We present ProtoPeer, a peer-to-peer systems prototyping toolkit that allows for switching between the event driven simulation and live network deployment without changing any of the application code. ProtoPeer exports a set of APIs for message passing, message queuing, timer operations as well as overlay routing and managing the overlay neighbors. Users can plug in their own custom implementations of most of the parts of ProtoPeer including custom network models for simulation and custom message passing over transports other than the default TCP/UDP.

2008