JMS and AMQP

 

I am trying to understand what JMS and how it is connected to AMQP terminology. I know JMS is an API and AMQP is a protocol.

Here are my assumptions (and questions as well)

  • RabbitMQ uses AMQP protocol (rather implements AMQP protocol)
  • Java clients need to use AMQP protocol client libraries to connect / use RabbitMQ
  • Where does JMS API come into play here? JMS API should use AMQP client libraries to connect to RabbitMQ?
  • Usually we use JMS to connect Message brokers like RabbitMQ, ActiveMQ, etc. Then what is the default protocol used here instead of AMQP?

    • Some of the above may be dumb. :-) But trying to wrap my head around it.

    Your question is a bit messy and resembles a tough question in a question paper :) (As teachers always try to ask simple questions making complex :DI hope you are not a teacher :) ) Let's see all of these one by one.

    As you know:

    The Java Message Service (JMS) API is a Java Message Oriented Middleware (MOM) API for sending messages between two or more clients . JMS is a part of the Java Platform, Enterprise Edition, and is defined by a specification developed under the Java Community Process as JSR 914. It is a messaging standard that allows application components based on the Java Enterprise Edition (Java EE) to create, send, receive, and read messages. It allows the communication between different components of a distributed application to be loosely coupled, reliable, and asynchronous .

    Now (from Wikipedia):

    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.

    And the most important thing (again from Wikipedia):

    Unlike JMS, which merely defines an API, 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 octets. 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

    Some important things you should know:

  • Keep in mind that AMQP is a messaging technology that do not implement the JMS API.
  • JMS is API and AMQP is a protocol.So it doesn't make sense to say that what is default protocol of JMS, of course client applications use HTTP/S as the connection protocol when invoking a WebLogic Web Service.
  • JMS is only a API spec. It doesn't use any protocol. A JMS provider (like ActiveMQ) could be using any underlying protocol to realize the JMS API. For ex: Apache ActiveMQ can use any of the following protocols: AMQP, MQTT, OpenWire, REST(HTTP), RSS and Atom, Stomp, WSIF, WS Notification, XMPP. I suggest you read Using JMS Transport as the Connection Protocol.

    • Good Luck :)

    Let's start from the basis.

    RabbitMQ is a MOM (Message Oriented Middleware), developed with Erlang (a TLC-oriented programming language) and implementing the wire protocol AMQP (Advance Message Queuing Protocol). Currently, many Client APIs (eg, Java, C++, RESTful, etc.) are available to enable the usage of RabbitMQ messaging services.

    JMS (Java Messaging Service) is a JCP standard defining a set of structured APIs to be implemented by a MOM. An example of MOM that implements (ie is compatible with) the JMS APIs is ActiveMQ; there's also HornetMQ, and others. Such middlewares get the JMS APIs and implement the exchange patterns accordingly.

    According to above, taken the skeleton of JMS APIs, an instance of RabbitMQ and its Java Client APIs, it is possible to develop a JMS implementation making use of RabbitMQ: the only thing that one has to do, at that point, is implementing the exchange pattern (over RabbitMQ) according to the JMS specification.

    The key is: a set of APIs, like JMS, can be implemented no matter of the technology (in this case, RabbitMQ).

    JMS, when it was defined did not define a protocol between the JMS client and a messaging server. The JMS client, which implement the JMS API can use whatever protocol to communicate with messaging server. The client just need to be compliant with JMS api. Thats all. Ususally JMS clients use a custom protocol that their messaging server understands.

    AMQP on other hand is a protocol between a messaging client and messaging server. A JMS client can use AMQP as the protocol to communicate with the messaging server. And there are clients like that available.

    http://www.lshift.net/blog/2009/03/16/openamqs-jms-client-with-rabbitmq-server

    链接地址: http://www.djcxy.com/p/34116.html

    上一篇: Rabbit MQ用法

    下一篇: JMS和AMQP