CAMEL-14191: EIP docs - Add links to last EIP patterns and add new pages if missing content
diff --git a/docs/user-manual/modules/ROOT/assets/images/eip/CDC-Debezium.png b/docs/user-manual/modules/ROOT/assets/images/eip/CDC-Debezium.png
new file mode 100644
index 0000000..bf859a9
--- /dev/null
+++ b/docs/user-manual/modules/ROOT/assets/images/eip/CDC-Debezium.png
Binary files differ
diff --git a/docs/user-manual/modules/ROOT/assets/images/eip/MessagingBridge.gif b/docs/user-manual/modules/ROOT/assets/images/eip/MessagingBridge.gif
new file mode 100644
index 0000000..6010f92
--- /dev/null
+++ b/docs/user-manual/modules/ROOT/assets/images/eip/MessagingBridge.gif
Binary files differ
diff --git a/docs/user-manual/modules/ROOT/assets/images/eip/MessagingBridgeIcon.gif b/docs/user-manual/modules/ROOT/assets/images/eip/MessagingBridgeIcon.gif
new file mode 100644
index 0000000..6154d53
--- /dev/null
+++ b/docs/user-manual/modules/ROOT/assets/images/eip/MessagingBridgeIcon.gif
Binary files differ
diff --git a/docs/user-manual/modules/ROOT/pages/change-data-capture.adoc b/docs/user-manual/modules/ROOT/pages/change-data-capture.adoc
new file mode 100644
index 0000000..6acee85
--- /dev/null
+++ b/docs/user-manual/modules/ROOT/pages/change-data-capture.adoc
@@ -0,0 +1,17 @@
+[[Change-Data-Capture]]
+= Change Data Capture
+
+Camel supports the https://en.wikipedia.org/wiki/Change_data_capture[Change Data Capture] pattern.
+
+This patterns allows to track changes in databases, and then let applications listen to change events,
+and react accordingly. For example this can be used as a xref:messaging-brdige[Messaging Bridge] to
+bridge two systems.
+
+image::eip/CDC-Debezium.png[image]
+
+Camel integrates with https://debezium.io/[Debezium] which is a CDC system. There are a number of Camel Debezium
+components that works with different databases such as MySQL, Postgres, and MongoDB.
+
+== Sample
+
+See the https://github.com/apache/camel/tree/master/examples/camel-example-debezium[Camel Debezium Example] for more details.
\ No newline at end of file
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 c2094a8..27e8989 100644
--- a/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
+++ b/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
@@ -58,20 +58,28 @@
|xref:dead-letter-channel.adoc[Dead Letter Channel] |What will the
messaging system do with a message it cannot deliver?
-a|image::eip/ChannelAdapterIcon.gif[image]
-|xref:channel-adapter.adoc[Channel Adapter] |How can you connect an
-application to the messaging system so that it can send and receive messages?
-
a|image::eip/GuaranteedMessagingIcon.gif[image]
|xref:guaranteed-delivery.adoc[Guaranteed Delivery] |How can the sender
make sure that a message will be delivered, even if the messaging system
fails?
+a|image::eip/ChannelAdapterIcon.gif[image]
+|xref:channel-adapter.adoc[Channel Adapter] |How can you connect an
+application to the messaging system so that it can send and receive messages?
+
+a|image::eip/MessagingBridgeIcon.gif[image]
+|xref:messaging-bridge.adoc[Messaging Bridge] |How can multiple messaging systems
+be connected so that messages available on one are also available on the others??
+
a|image::eip/MessageBusIcon.gif[image]
|xref:message-bus.adoc[Message Bus] |What is an architecture that
enables separate applications to work together, but in a de-coupled
fashion such that applications can be easily added or removed without
affecting the others?
+
+a|image::eip/MessagingBridgeIcon.gif[image]
+|xref:change-data-capture.adoc[Change Data Capture] | Data synchronization by capturing
+changes made to a database, and apply those changes to another system.
|=======================================================================
[[EnterpriseIntegrationPatterns-MessageConstruction]]
diff --git a/docs/user-manual/modules/ROOT/pages/messaging-bridge.adoc b/docs/user-manual/modules/ROOT/pages/messaging-bridge.adoc
new file mode 100644
index 0000000..23ba8f9
--- /dev/null
+++ b/docs/user-manual/modules/ROOT/pages/messaging-bridge.adoc
@@ -0,0 +1,24 @@
+[[Messaging-Bridge]]
+= Messaging Bridge
+
+Camel supports the
+https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessagingBridge.html[Messaging Bridge]
+from the xref:enterprise-integration-patterns.adoc[EIP patterns].
+
+How can multiple messaging systems be connected so that messages available on one are also available on the others?
+
+image::eip/MessagingBridge.gif[image]
+
+Use a Messaging Bridge, a connection between messaging systems, to replicate messages between systems.
+
+You can use Camel to bridge different systems using Camel components and routes.
+
+A basic bridge between two queues can be done with a Camel route:
+
+[source,java]
+----
+from("mq:queue:foo")
+ .to("activemq:queue:foo")
+----
+
+Another alternative is to bridge systems using xref:change-data-capture.adoc[Change Data Capture].
\ No newline at end of file
