Amqp specifications-1. Introduction

 

Introduction

Overview

Amqp is an open Internet protocol for business message systems ). Amqp can be divided into separate layers. At the lowest level, we define an efficient binary Point-to-Point Protocol for transmitting messages between two processes on the network. Secondly, we define an abstract Message format that focuses on standard encoding. Every process compatible with the amqp protocol must be able to use this Standard Message format to send and receive messages.

 

Principles and Use Cases

The user community of the business message system defines amqp requirements based on their experience in building and operating the network information processing system. Amqp Working Group is a measure of the success of amqp Based on the fulfillment of this agreement and these requirements. These requirements are outlined as follows.

 

Universality

1.0 open Internet protocol standards support (a) convenient use, (B) implementation, and (c) extension.

The core functions are clear and clear, and support business message routing and delivery on the network infrastructure. Therefore, the infrastructure can provide business message processing without professional integration experience.

Low understanding, use, and implementation thresholds.

1.0 it can be integrated into the existing enterprise message application environment in practical ways.

 

Security and credibility

1.0 can be used as a secure and trusted network infrastructure that supports global transactions.

L as evidence of anti-tampering of business messages.

L supports message persistence independent from the receiver.

L and message delivery is recoverable for technical failures.

1.0 support the business needs for transmitting any economically valuable transactions.

FutureThe recipient and the sender agree that there is no spam data injection.

 

Accuracy

1.0 define the meanings of messagequeueing and delivery, including at-least-once (at-least-once) and at-least-once (at-least-once ); once (once-and-only-once), reliability.

1.0 clearly defines the meaning of messageordering, which describes what the sender can expect the receiver or queue manager to observe.

1.0 clear semantics of "reliable Failure Handling" (reliablefailure), all exceptions can be managed.

 

Applicability

1.0 as TCP is one of the technical features of network communication, we hope that amqp will become a popular business message technology tool for various organizations. As it increases, the ROI increases and the cost (TCO) decreases.

Any amqp client can create a connection to any amqp proxy through TCP and session with it.

FutureAny amqp client can create a connection to any amqp proxy through other alternative protocols supported by both parties (such as sctp, UDP/multicast, and so on) and session with it.

1.0 a set of core message modes are provided through a single manageable Protocol: asynchronous oriented message, request/response, publishing/subscription, storage/distribution.

1.0 supports a message topology that is radiating inside and outside the business boundary.

FutureA clear protocol for inter-agency authentication is developed to support message transmission from the center to the center across message boundaries.

Interactivity

More than 1.0 stable and interoperable proxies can come from completely independent sources, including design, architecture, code, and owner.

1.0 the implementation of any proxy is consistent with all mandatory message exchange and queue functions, including clear semantics.

1.0 the implementation is available for independent testing and verification by anyone.

1.0 the transport protocol kernel between the client and the proxy is stable, so with 1. the features of Version X have evolved, so agents do not have to be upgraded: Any 1. the client of Version X can be. if y> = x.

FutureThe Protocol extension between the proxy and proxy is stable, so with 1. the proxy does not need to be upgraded as the feature of Version X evolves: if the two Agent versions are 1. X and 1.y. they can use 1. X communication, if X <Y.

1.0 layered architecture, So feature and network transmission can be scaled independently by different communities using them, so that business integration with other systems does not require coordination by the amqp Working Group.

 

Ease of use

1.0 binary transfer protocol, so it is universal, fast, and can be embedded (the top layer can be XML ). The packaging system can also provide management features, such as control systems, middleware, and telephones.

1.0 scalable: as a result, it can be used as an infrastructure for a high-performance, fault-tolerant, and reliable messaging system without the need for other messaging technologies.

FutureIt is possible to interact with other message delivery systems. It is sufficient to use management standards to manage message systems to integrate various popular business operations.

FutureIntermediary: supports route and relay management, traffic management, and service quality management.

FutureDecentralized deployment: local independent governance.

FutureGlobal addressing: standardizes end-to-end delivery across any network range.

 

How to read standards

Amqp standards are divided into different chapters to define different parts of the standards. You may wish to read from a specific chapter based on your fields of interest and use other chapters as a reference.

 

Chapter 1 defines the amqp Type System

Chapter 2 defines the transmission layer of amqp

Chapter 3 defines the message passing layer of amqp

Chapter 4 define the Transaction layer of amqp

Chapter 5 defines the security layer of amqp