Misplaced Pages

#135864

52-440: 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

104-420: A URL . Likewise a map value containing key-value pairs for 'name', 'address' etc., might be annotated as being a representation of a 'customer' type. The type-system is used to define a message format allowing standard and extended meta-data to be expressed and understood by processing entities. It is also used to define the communication primitives through which messages are exchanged between such entities, i.e.

156-742: A royalty-free basis. Many definitions of the term standard permit patent holders to impose " reasonable and non-discriminatory licensing" royalty fees and other licensing terms on implementers or users of the standard. For example, the rules for standards published by the major internationally recognized standards bodies such as the Internet Engineering Task Force (IETF), International Organization for Standardization (ISO), International Electrotechnical Commission (IEC), and ITU-T permit their standards to contain specifications whose implementation will require payment of patent licensing fees. Among these organizations, only

208-624: A "free software and open standards law." The decree includes the requirement that the Venezuelan public sector must use free software based on open standards, and includes a definition of open standard: Solace systems Solace (formerly Solace Systems ) is a middleware company based in Kanata / Ottawa , Ontario , Canada, that manufactures and sells message-oriented middleware  appliances and software that routes information between applications, devices and user interfaces. Solace

260-498: A body, which AMQP refers to as application data. Properties are specified in the AMQP type system, as are annotations. The application data can be of any form, and in any encoding the application chooses. One option is to use the AMQP type system to send structured, self-describing data. The link protocol transfers messages between two nodes but assumes very little as to what those nodes are or how they are implemented. A key category

312-681: A common patent policy under the banner of the WSC . However, the ITU-T definition should not necessarily be considered also applicable in ITU-R, ISO and IEC contexts, since the Common Patent Policy does not make any reference to "open standards" but rather only to "standards." In section 7 of its RFC 2026, the IETF classifies specifications that have been developed in a manner similar to that of

364-402: A data format which is made public, is thoroughly documented and neutral with regard to the technological tools needed to peruse the same data. The E-Government Interoperability Framework (e-GIF) defines open standard as royalty-free according to the following text: While a universally agreed definition of "open standards" is unlikely to be resolved in the near future, the e-GIF accepts that

416-606: A definition of "open standards" needs to recognise a continuum that ranges from closed to open, and encompasses varying degrees of "openness." To guide readers in this respect, the e-GIF endorses "open standards" that exhibit the following properties: The e-GIF performs the same function in e-government as the Road Code does on the highways. Driving would be excessively costly, inefficient, and ineffective if road rules had to be agreed each time one vehicle encountered another. The Portuguese Open Standards Law, adopted in 2011, demands

468-535: A definition of open standards, which also is used in pan-European software development projects. It states: The French Parliament approved a definition of "open standard" in its "Law for Confidence in the Digital Economy." The definition is (Article 4): A clear royalty-free stance and far reaching requirements case is the one for India's Government 4.1 Mandatory Characteristics An Identified Standard will qualify as an "Open Standard", if it meets

520-605: A full, irrevocable and irreversible way to the Portuguese State; e) There are no restrictions to its implementation. A Law passed by the Spanish Parliament requires that all electronic services provided by the Spanish public administration must be based on open standards. It defines an open standard as royalty-free, according to the following definition (ANEXO Definiciones k): An open standard fulfills

572-460: 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 bytes . Consequently, any tool that can create and interpret messages that conform to this data format can interoperate with any other compliant tool irrespective of implementation language. AMQP is a binary application layer protocol, designed to efficiently support

SECTION 10

#1732790168136

624-432: A number of definitions of open standards which emphasize different aspects of openness, including the openness of the resulting specification, the openness of the drafting process, and the ownership of rights in the standard. The term "standard" is sometimes restricted to technologies approved by formalized committees that are open to participation by all interested parties and operate on a consensus basis. The definitions of

676-598: A set of principles which have contributed to the exponential growth of the Internet and related technologies. The "OpenStand Principles" define open standards and establish the building blocks for innovation. Standards developed using the OpenStand principles are developed through an open, participatory process, support interoperability, foster global competition, are voluntarily adopted on a global level and serve as building blocks for products and services targeted to meet

728-614: A wide variety of messaging applications and communication patterns. It provides flow controlled, 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 multiple times) and exactly-once (where the message will always certainly arrive and do so only once), and authentication and/or encryption based on SASL and/or TLS . It assumes an underlying reliable transport layer protocol such as Transmission Control Protocol (TCP). The AMQP specification

780-401: Is a bidirectional, sequential conversation between two peers that is initiated with a begin frame and terminated with an end frame. A connection between two peers can have multiple sessions multiplexed over it, each logically independent. Connections are initiated with an open frame in which the sending peer's capabilities are expressed, and terminated with a close frame. AMQP defines as

832-461: Is defined in several layers: (i) a type system, (ii) a symmetric, asynchronous protocol for the transfer of messages from one process to another, (iii) a standard, extensible message format and (iv) a set of standardised but extensible 'messaging capabilities.' AMQP was originated in 2003 by John O'Hara at JPMorgan Chase in London . AMQP was conceived as a co-operative open effort. The initial design

884-714: Is determined by the market. The ITU-T is a standards development organization (SDO) that is one of the three sectors of the International Telecommunication Union (a specialized agency of the United Nations ). The ITU-T has a Telecommunication Standardization Bureau director's Ad Hoc group on IPR that produced the following definition in March 2005, which the ITU-T as a whole has endorsed for its purposes since November 2005: The ITU-T , ITU-R , ISO , and IEC have harmonized on

936-557: Is here meant in the sense of fulfilling the following requirements: The Network Centric Operations Industry Consortium (NCOIC) defines open standard as the following: Specifications for hardware and/or software that are publicly available implying that multiple vendors can compete directly based on the features and performance of their products. It also implies that the existing open system can be removed and replaced with that of another vendor with minimal effort and without major interruption. The Danish government has attempted to make

988-527: Is the current specification version. It focuses on core features which are necessary for interoperability at Internet scale. It contains less explicit routing than previous versions because core functionality is the first to be rigorously standardized. AMQP 1.0 interoperability has been more extensively tested with more implementors than prior versions. The AMQP website contains the OASIS specification for version 1.0 . Earlier versions of AMQP, published prior to

1040-506: Is then published in the form of RFC 6852 in January 2013. The European Union defined the term for use within its European Interoperability Framework for Pan-European eGovernment Services, Version 1.0 although it does not claim to be a universal definition for all European Union use and documentation. To reach interoperability in the context of pan-European eGovernment services, guidance needs to focus on open standards. The word "open"

1092-626: Is those nodes used as a rendezvous point between senders and receivers of messages (e.g. queues or topics ). The AMQP specification calls such nodes distribution nodes and codifies some common behaviors. This includes: Though AMQP can be used in simple peer-to-peer systems, defining this framework for messaging capabilities additionally enables interoperability with messaging intermediaries (brokers, bridges etc.) in larger, richer messaging networks. The framework specified covers basic behaviors but allows for extensions to evolve that can be further codified and standardised. AMQP protocol version 1.0

SECTION 20

#1732790168136

1144-427: Is wrong with AMQP (and how to fix it)" and distributed it to the working group to alert of imminent failure, identify problems seen by iMatix and propose ways to fix the AMQP specification. By then, iMatix had already started work on ZeroMQ . In 2010, Hintjens announced that iMatix would leave the AMQP workgroup and did not plan to support AMQP/1.0 in favor of the significantly simpler and faster ZeroMQ. In August 2011,

1196-759: The GSM phones (adopted as a government standard), Open Group which promotes UNIX , and the Internet Engineering Task Force (IETF) which created the first standards of SMTP and TCP/IP. Buyers tend to prefer open standards which they believe offer them cheaper products and more choice for access due to network effects and increased competition between vendors. Open standards which specify formats are sometimes referred to as open formats . Many specifications that are sometimes referred to as standards are proprietary, and only available (if they can be obtained at all) under restrictive contract terms from

1248-489: The bare message , that part of the message that is created by the sending application. This is considered immutable as the message is transferred between one or more processes. Ensuring the message as sent by the application is immutable allows for end-to-end message signing and/or encryption and ensures that any integrity checks (e.g. hashes or digests ) remain valid. The message can be annotated by intermediaries during transit, but any such annotations are kept distinct from

1300-419: The transfer frame. Messages on a link flow in only one direction. Transfers are subject to a credit-based flow control scheme, managed using flow frames. This allows a process to protect itself from being overwhelmed by too large a volume of messages or more simply to allow a subscribing link to pull messages as and when desired. Each transferred message must eventually be settled . Settlement ensures that

1352-611: The "Simplified BSD License" as stated in the IETF Trust Legal Provisions and Copyright FAQ based on RFC 5377. In August 2012, the IETF combined with the W3C and IEEE to launch OpenStand and to publish The Modern Paradigm for Standards. This captures "the effective and efficient standardization processes that have made the Internet and Web the premiere platforms for innovation and borderless commerce". The declaration

1404-444: The 1.0 specification. Whilst AMQP originated in the financial services industry, it has general applicability to a broad range of middleware problems. AMQP defines a self-describing encoding scheme allowing interoperable representation of a wide range of commonly used types. It also allows typed data to be annotated with additional meaning, for example a particular string value might be annotated so that it could be understood as

1456-468: The AMQP frame bodies . The basic unit of data in AMQP is a frame . There are nine AMQP frame bodies defined that are used to initiate, control and tear down the transfer of messages between two peers. These are: The link protocol is at the heart of AMQP. An attach frame body is sent to initiate a new link; a detach to tear down a link. Links may be established in order to receive or send messages. Messages are sent over an established link using

1508-477: The AMQP working group announced its reorganization into an OASIS member section. AMQP 1.0 was released by the AMQP working group on 30 October 2011, at a conference in New York. At the event Microsoft, Red Hat, VMware , Apache, INETCO and IIT Software demonstrated software running the protocol in an interoperability demonstration. The next day, on 1 November 2011, the formation of an OASIS Technical Committee

1560-495: The IETF and ITU-T explicitly refer to their standards as "open standards", while the others refer only to producing "standards". The IETF and ITU-T use definitions of "open standard" that allow "reasonable and non-discriminatory" patent licensing fee requirements. There are those in the open-source software community who hold that an "open standard" is only open if it can be freely adopted, implemented and extended. While open standards or architectures are considered non-proprietary in

1612-518: The IETF itself as being "open standards," and lists the standards produced by ANSI , ISO , IEEE , and ITU-T as examples. As the IETF standardization processes and IPR policies have the characteristics listed above by ITU-T, the IETF standards fulfill the ITU-T definition of "open standards." However, the IETF has not adopted a specific definition of "open standard"; both RFC 2026 and the IETF's mission statement (RFC 3935) talks about "open process," but RFC 2026 does not define "open standard" except for

Advanced Message Queuing Protocol - Misplaced Pages Continue

1664-474: The JMS-compliant messaging system in use may need to be deployed on both client and server. On the other hand, AMQP is a wire-level protocol specification. In theory AMQP provides interoperability as different AMQP-compliant software can be deployed on the client and server sides. Open standard The terms open and standard have a wide range of meanings associated with their usage. There are

1716-649: The degree of openness will be taken into account when selecting an appropriate standard: The UK government 's definition of open standards applies to software interoperability, data and document formats. The criteria for open standards are published in the "Open Standards Principles" policy paper and are as follows. The Cabinet Office in the UK recommends that government departments specify requirements using open standards when undertaking procurement exercises in order to promote interoperability and re-use, and avoid technological lock-in. The Venezuelan Government approved

1768-506: The following conditions: The South African Government approved a definition in the "Minimum Interoperability Operating Standards Handbook" (MIOS). For the purposes of the MIOS, a standard shall be considered open if it meets all of these criteria. There are standards which we are obliged to adopt for pragmatic reasons which do not necessarily fully conform to being open in all respects. In such cases, where an open standard does not yet exist,

1820-581: The following criteria: Italy has a general rule for the entire public sector dealing with Open Standards, although concentrating on data formats, in Art. 68 of the Code of the Digital Administration ( Codice dell'Amministrazione Digitale ) [applications must] allow representation of data under different formats, at least one being an open data format. [...] [it is defined] an open data format,

1872-506: The immutable bare message . Annotations may be added before or after the bare message. The header is a standard set of delivery-related annotations that can be requested or indicated for a message and includes time to live, durability, priority. The bare message itself is structured as an optional list of standard properties (message id, user id, creation time, reply to, subject, correlation id, group id etc.), an optional list of application-specific properties (i.e., extended properties) and

1924-400: The needs of markets and consumers. This drives innovation which, in turn, contributes to the creation of new markets and the growth and expansion of existing markets. There are five, key OpenStand Principles, as outlined below: 1. Cooperation Respectful cooperation between standards organizations, whereby each respects the autonomy, integrity, processes, and intellectual property rules of

1976-411: The organization that owns the copyright on the specification. As such these specifications are not considered to be fully open . Joel West has argued that "open" standards are not black and white but have many different levels of "openness". A more open standard tends to occur when the knowledge of the technology becomes dispersed enough that competition is increased and others are able to start copying

2028-711: The others. 2. Adherence to Principles – Adherence to the five fundamental principles of standards development, namely 3. Collective Empowerment Commitment by affirming standards organizations and their participants to collective empowerment by striving for standards that: 4. Availability Standards specifications are made accessible to all for implementation and deployment. Affirming standards organizations have defined procedures to develop specifications that can be implemented under fair terms. Given market diversity, fair terms may vary from royalty-free to fair, reasonable, and non-discriminatory terms (FRAND). 5. Voluntary Adoption Standards are voluntarily adopted and success

2080-647: The purpose of defining what documents IETF standards can link to. RFC 2026 belongs to a set of RFCs collectively known as BCP 9 (Best Common Practice, an IETF policy). RFC 2026 was later updated by BCP 78 and 79 (among others). As of 2011 BCP 78 is RFC 5378 (Rights Contributors Provide to the IETF Trust), and BCP 79 consists of RFC 3979 (Intellectual Property Rights in IETF Technology) and a clarification in RFC 4879. The changes are intended to be compatible with

2132-487: The release of 1.0 (see History above) and significantly different from it, include: These open protocol specifications cover the same or a similar space as AMQP: Java Message Service (JMS), is often compared to AMQP. However, JMS is an API specification (part of the Java EE specification) that defines how message producers and consumers are implemented. JMS does not guarantee interoperability between implementations, and

Advanced Message Queuing Protocol - Misplaced Pages Continue

2184-451: 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

2236-419: The sender and receiver agree on the state of the transfer, providing reliability guarantees. Changes in state and settlement for a transfer (or set of transfers) are communicated between the peers using the disposition frame. Various reliability guarantees can be enforced this way: at-most-once, at-least-once and exactly-once. Multiple links, in both directions, can be grouped together in a session . A session

2288-485: The sense that the standard is either unowned or owned by a collective body, it can still be publicly shared and not tightly guarded. The typical example of "open source" that has become a standard is the personal computer originated by IBM and now referred to as Wintel , the combination of the Microsoft operating system and Intel microprocessor. There are three others that are most widely accepted as "open" which include

2340-702: The technology as they implement it. This occurred with the Wintel architecture as others were able to start imitating the software. Less open standards exist when a particular firm has much power (not ownership) over the standard, which can occur when a firm's platform "wins" in standard setting or the market makes one platform most popular. On August 12, 2012, the Institute of Electrical and Electronics Engineers (IEEE), Internet Society (ISOC), World Wide Web Consortium (W3C), Internet Engineering Task Force (IETF) and Internet Architecture Board (IAB), jointly affirmed

2392-664: The term open standard used by academics, the European Union , and some of its member governments or parliaments such as Denmark , France , and Spain preclude open standards requiring fees for use, as do the New Zealand , South African and the Venezuelan governments. On the standard organisation side, the World Wide Web Consortium (W3C) ensures that its specifications can be implemented on

2444-667: The use of Open Standards, and is applicable to sovereign entities, central public administration services (including decentralized services and public institutes), regional public administration services and the public sector. In it, Open Standards are defined thus: a) Its adoption is fruit off an open decision process accessible to all interested parties; b) The specifications document must have been freely published, allowing its copy, distribution and use without restrictions; c) The specifications document cannot cover undocumented actions of processes; d) The applicable intellectual property rights, including patents, have been made available in

2496-525: Was announced to advance this contributed AMQP version 1.0 through the international open standards process. The first draft from OASIS was released in February 2012, the changes as compared to that published by the Working Group being restricted to edits for improved clarity (no functional changes). The second draft was released for public review on 20 June (again with no functional changes), and AMQP

2548-1138: Was approved as an OASIS standard on 31 October 2012. OASIS AMQP was approved for release as an ISO and IEC International Standard in April 2014. AMQP 1.0 was balloted through the Joint Technical Committee on Information Technology (JTC1) of the International Standards Organization (ISO) and the International Electrotechnical Commission (IEC). The approved OASIS AMQP submission has been given the designation, ISO/IEC 19464. Previous versions of AMQP were 0-8, published in June 2006, 0-9, published in December 2006, 0-10 published in February 2008 and 0-9-1, published in November 2008. These earlier releases are significantly different from

2600-534: Was by JPMorgan Chase from mid-2004 to mid-2006 and it contracted iMatix Corporation to develop a C broker and protocol documentation. In 2005 JPMorgan Chase approached other firms to form a working group that included Cisco Systems , IONA Technologies , iMatix, Red Hat , and Transaction Workflow Innovation Standards Team (TWIST). In the same year JPMorgan Chase partnered with Red Hat to create Apache Qpid , initially in Java and soon after C++. Independently, RabbitMQ

2652-819: Was developed in Erlang by Rabbit Technologies, followed later by the Microsoft and StormMQ implementations. The working group grew to 23 companies including Bank of America , Barclays , Cisco Systems, Credit Suisse , Deutsche Börse , Goldman Sachs , HCL Technologies Ltd , Progress Software , IIT Software , INETCO Systems Limited , Informatica (including 29 West), JPMorgan Chase, Microsoft Corporation , my-Channels, Novell , Red Hat , Software AG , Solace Systems , StormMQ, Tervela Inc. , TWIST Process Innovations ltd, VMware (which acquired Rabbit Technologies) and WSO2 . In 2008, Pieter Hintjens , CEO and chief software designer of iMatix, wrote an article called "What

SECTION 50

#1732790168136

2704-482: Was founded in 2001 by Craig Betts, with the idea of embedding messaging functionality in hardware. Between then and 2016, the company raised more than $ 60 million from venture capital firms. In 2016, New York equity firm Bridge Growth Partners acquired a majority stake in Solace with an investment of more than $ 100 million. In 2017, former Halogen Software CEO Les Rechan was hired as CEO of Solace, with Betts serving as

#135864