This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 1d123ec43996bda713dc928f074ffd56e0315665
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Fri Nov 22 15:51:26 2019 +0100
CAMEL-14191: EIP docs - Add links to last EIP patterns and add new pages if
missing content
---
.../ROOT/assets/images/eip/MessageBroker.gif | Bin 0 -> 1686 bytes
.../ROOT/assets/images/eip/MessageBrokerIcon.gif | Bin 0 -> 547 bytes
.../ROOT/pages/enterprise-integration-patterns.adoc | 5 +++++
.../modules/ROOT/pages/message-broker.adoc | 20 ++++++++++++++++++++
4 files changed, 25 insertions(+)
diff --git a/docs/user-manual/modules/ROOT/assets/images/eip/MessageBroker.gif
b/docs/user-manual/modules/ROOT/assets/images/eip/MessageBroker.gif
new file mode 100644
index 0000000..3ddef7b
Binary files /dev/null and
b/docs/user-manual/modules/ROOT/assets/images/eip/MessageBroker.gif differ
diff --git
a/docs/user-manual/modules/ROOT/assets/images/eip/MessageBrokerIcon.gif
b/docs/user-manual/modules/ROOT/assets/images/eip/MessageBrokerIcon.gif
new file mode 100644
index 0000000..e97a88e
Binary files /dev/null and
b/docs/user-manual/modules/ROOT/assets/images/eip/MessageBrokerIcon.gif differ
diff --git
a/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
b/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
index cef0080..53faf62 100644
--- a/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
+++ b/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
@@ -168,6 +168,11 @@ a|image::eip/ProcessManagerIcon.gif[image]
through multiple processing steps when the required steps may not be known
at design-time and may not be sequential?
+a|image::eip/MessageBrokerIcon.gif[image]
+|xref:message-broker.adoc[Message Broker] |How can you decouple the
+destination of a message from the sender and maintain central control
+over the flow of messages?
+
|
|xref:throttle-eip.adoc[Throttler] |How can I throttle messages to ensure
that a specific endpoint does not get overloaded, or we don't exceed an
diff --git a/docs/user-manual/modules/ROOT/pages/message-broker.adoc
b/docs/user-manual/modules/ROOT/pages/message-broker.adoc
new file mode 100644
index 0000000..9f101e7
--- /dev/null
+++ b/docs/user-manual/modules/ROOT/pages/message-broker.adoc
@@ -0,0 +1,20 @@
+[[Message-Broker]]
+= Message Broker
+
+Camel supports the
+https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageBroker.html[Message
Broker]
+from the xref:enterprise-integration-patterns.adoc[EIP patterns] book.
+
+How can you decouple the destination of a message from the sender and maintain
central control over the flow of messages?
+
+image::eip/MessageBroker.gif[image]
+
+Use a central Message Broker that can receive messages from multiple
destinations,
+determine the correct destination and route the message to the correct channel.
+
+Camel supports integration with existing message broker systems such as Apache
ActiveMQ,
+Apache Kafka, RabbitMQ, and cloud queue systems such as AWS SQS, and others.
+
+These Camel components allows to both send and receive data from message
brokers.
+
+
