DBZ-2096 Add Debezium Server section to architecture.adoc
This commit is contained in:
parent
317383be30
commit
8af890c8a5
Binary file not shown.
After Width: | Height: | Size: 71 KiB |
@ -27,6 +27,18 @@ Depending on the chosen sink connector, it may be needed to apply {prodname}'s {
|
||||
which will only propagate the "after" structure from {prodname}'s event envelope to the sink connector.
|
||||
|
||||
ifdef::community[]
|
||||
== {prodname} server
|
||||
|
||||
Another way to deploy {prodname} is using the xref:operations/debezium-server.adoc[standalone server].
|
||||
The {prodname} server is a read-to-use application that streams change events from the source database to a variety of messaging infrastructures.
|
||||
|
||||
The following image shows the architecture of a CDC pipeline using the {prodname} server:
|
||||
|
||||
image:debezium-server-architecture.png[{prodname} Architecture]
|
||||
|
||||
The {prodname} server is configured to use one of the {prodname} source connectors to capture changes from the source database.
|
||||
By default, the changes from one capture table in the source database are emitted as change records and consumed by one of a variety of sink messaging infrastructures like Amazon Kinesis, Google Cloud Pub/Sub, or Apache Pulsar.
|
||||
|
||||
== Embedded Engine
|
||||
|
||||
An alternative way for using the {prodname} connectors is the xref:operations/embedded.adoc[embedded engine].
|
||||
|
Loading…
Reference in New Issue
Block a user