Github user gemmellr commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/1607#discussion_r146818341
--- Diff: docs/user-manual/en/kafka-bridges.md ---
@@ -0,0 +1,180 @@
+# Apache ActiveMQ Kafka Bridge
+
+The function of a bridge is to consume messages from a source queue in
Apache ActiveMQ Artemis,
+and forward them to a target topic, on a remote Apache Kafka server.
+
+By pairing Apache ActiveMQ Artemis and Apache Kafka with the bridge you
could have a hybrid broker setup,
+having a data flow with CORE, AMQP, MQTT clients, as well as now Kafka
clients also.
+Taking and giving the best features of both broker technologies when and
where needed for a flow of data.
+
+
+
+The intent is this will be a two way bridge, but currently the flow is a
single direction
+from Apache ActiveMQ Artemis to Apache Kafka
+
+
+The source and target servers are remote making bridging suitable
+for reliably sending messages from one artemis cluster to kafka,
+for instance across a WAN, to the cloud, or internet and where the
connection may be unreliable.
+
+The bridge has built in resilience to failure so if the target server
+connection is lost, e.g. due to network failure, the bridge will retry
+connecting to the target until it comes back online. When it comes back
+online it will resume operation as normal.
+
+
--- End diff --
The (JMS / Proton) qualifier should be removed from the AMQP Client box.
Other clients are available, etc.
I'd say the same for JMS in the JMS Core Client box, if it also works for
the non-JMS client.
---
