The Qpid project offers two kinds of components, messaging APIs for building AMQP applications, and messaging servers for deploying AMQP networks. You can use them together to build robust distributed applications.
Messaging APIs give your application a tool for efficient, high-level interprocess communication.
Qpid offers three messaging APIs. Qpid Proton is a reactive API with full-spectrum AMQP control. In addition to being a messaging API, Qpid Proton is used by other Qpid components to implement AMQP 1.0 protocol support. Qpid JMS is an AMQP-fluent implementation of the widely used Java Message Service API. The Qpid Messaging API is a connection-oriented API that supports many languages.
Messaging servers are message-transfer intermediaries that provide additional services such as store-and-forward for improved reliability.
The Qpid message brokers are full-featured message-oriented middleware brokers. They offer specialized queueing behaviors, message persistence, and manageability. Qpid offers pure-Java and native-code implementations, the Java broker and the C++ broker.
Dispatch router is a different kind of messaging intermediary. It allows you to build redundant router networks connecting clients and brokers.
|C++ broker||-||Linux, Windows||1.0, 0-10|
|Java broker||-||JVM||1.0, 0-10, 0-9-1, 0-9, 0-8|
|Qpid JMS||Java||JVM||1.0, 0-10, 0-9-1, 0-9, 0-8|
|Qpid Messaging API||C++, Perl, Python, Ruby, .NET||Linux, Windows||1.0, 0-10|
The following components are no longer supported.
qpid::clientAPI, replaced by the Qpid Messaging API
Apache Qpid, Messaging built on AMQP; Copyright © 2013 The Apache Software Foundation; Licensed under the Apache License, Version 2.0; Apache Qpid, Qpid, Qpid Proton, Proton, Apache, the Apache feather logo, and the Apache Qpid project logo are trademarks of The Apache Software Foundation; All other marks mentioned may be trademarks or registered trademarks of their respective owners