Author: robbie
Date: Fri Mar 29 10:21:59 2019
New Revision: 1042750
Log:
refresh staged site bits with latest changes
Modified:
websites/production/activemq/content/activemq-website/components/nms/providers/amqp/index.html
Modified:
websites/production/activemq/content/activemq-website/components/nms/providers/amqp/index.html
==============================================================================
---
websites/production/activemq/content/activemq-website/components/nms/providers/amqp/index.html
(original)
+++
websites/production/activemq/content/activemq-website/components/nms/providers/amqp/index.html
Fri Mar 29 10:21:59 2019
@@ -92,7 +92,36 @@
<div class="container" >
<div class="row" style="margin-top: 30px">
<div class="col-12 nms">
- <p>Upon release, Apache NMS AMQP will provide an NMS layer for AMQP
1.0 support.</p>
+ <p><strong>NOTE:</strong> <em>This component is currently a work in
progress. This is info and developer docs, user docs such as downloads etc will
be added upon release.</em></p>
+
+<h3 id="overview">Overview</h3>
+<p>The goal of this project is to combine the <a href="../..">.NET Message
Service API</a> (NMS) with
+the <a href="https://www.amqp.org/";>Advanced Message Queuing Protocol
(AMQP)</a> 1.0 standard wireline protocol. Historically, the Apache community
created the NMS API which provided a vendor agnostic .NET interface to a
variety of messaging systems.</p>
+
+<p>The NMS API gives the flexibility to write .NET applications in C#, VB or
any other .NET language, all while using a single API to connect to any number
of messaging providers. The Advanced Message Queuing Protocol (AMQP) is an open
and standardized internet protocol for reliably passing messages between
applications or organizations.</p>
+
+<p>Before AMQP became a standard, organizations used proprietary wireline
protocols to connect their systems which lead to vendor lock-in and integration
problems when integrating with external organizations.</p>
+
+<p>The key to enabling vendor independence and mass adoption of technology is
to combine open source APIs and standard wireline protocols which is precisely
what this project is all about. Hereâs how AMQP 1.0 support within NMS
helps the .NET community:</p>
+<ul>
+ <li><strong>More Choice:</strong> As more message brokers and services
implement the AMQP 1.0 standard wireline, .NET developers and architects will
have more options for messaging technology.</li>
+ <li><strong>No Migration Risk:</strong> Since AMQP 1.0 is a wireline
standard, you wonât run into the problems that used to happen when switching
between implementations.</li>
+ <li><strong>Innovation:</strong> Competition is a key component of
technology innovation. Directly competitive messaging implementations, with
seamless pluggability, forces vendors to innovate and differentiate.</li>
+</ul>
+
+<h3 id="contributing">Contributing</h3>
+<p>If you are a .NET developer that doesnât want to be locked into a
messaging implementation then get engaged with this project. Here you will find
the open source code base and please provide comments and make your own
enhancements.</p>
+
+<p>Grab the Source from git
+https://github.com/apache/activemq-nms-amqp</p>
+
+<h4 id="overall-architecture">Overall Architecture</h4>
+<p>Apache-NMS-AMQP should bridge the familiar NMS concepts to AMQP protocol
concepts as described in the document <a
href="https://www.oasis-open.org/committees/download.php/60574/amqp-bindmap-jms-v1.0-wd09.pdf";>amqp-bindmap-jms-v1.0-wd09.pdf</a>.
+So in general most of the top level classes that implement the Apache.NMS
interface <em>Connection, Session, MessageProducer,</em> etc create, manage,
and destroy the amqpnetlite equivalent object <em>Connection, Session,
Link,</em> etc.</p>
+
+<h4 id="amqp10-protocol-engine-amqpnetlite">AMQP1.0 Protocol Engine
AmqpNetLite</h4>
+<p>Apache-NMS-AMQP uses <a
href="https://github.com/Azure/amqpnetlite";>AmqpNetLite</a> as the underlying
AMQP 1.0 transport Protocol engine.</p>
+
</div>
</div>
