maksaska commented on code in PR #11497:
URL: https://github.com/apache/ignite/pull/11497#discussion_r1976395208
##########
docs/_docs/extensions-and-integrations/change-data-capture-extensions.adoc:
##########
@@ -339,3 +553,132 @@ Configuration is done via Ignite node plugin:
</bean>
</property>
```
+
+== Common CDC strategies
+
+There are basically two strategies to choose from when it comes to CDC
replication with Apache Ignite, and a handful of options to configure the
transport for the data.
+
+* Strategies include `Active-Passive` and `Active-Active` replication regimes.
You can read it as 'from one cluster to another only' and 'from one cluster to
another and vice versa'.
+
+The former strategy implies that only one cluster would be actively used for
data consumption from the outside user application, while the other one
consumes data through CDC.
+
+The latter approach allows users to use both cluster simultaneously, meanwhile
the CDC clients transfer the updates between them. For that strategy to work,
the user should configure conflict resolver.
+
+* To make things work you have two independent tools to configure:
+
+** Thin/Thick clients for connection to destination clusters - responsible for
'put' operations on the destination cluster.
+
+** Ignite/Kafka driven middleman data transport - You can pass data through
Kafka topics, or you can use Ignite out of the box solution.
+
+Basically, you can combine them any way you want to meet your project goals.
+
+=== CDC example manager
+
+`ignite-cdc-ext` ships with CDC example manager `cdc-start-up.sh` alongside
`kafka-to-ignite.sh`. You can find it under
'$IGNITE_HOME/examples/config/cdc-start-up/' directory.
+
+You can use this script to start all kinds of replication strategies without
any additional configuration.
+
+The script will use predefined configuration '.xml' files from
'$IGNITE_HOME/examples/config/cdc-start-up/' directory. Feel free to examine
them as you try the manager out.
+
+NOTE: Use `--help` to explore the manager capabilities
+
+NOTE: Please, enable `ignite-rest-http` and `ignite-json` to be able to run
`cdc-start-up.sh` with `--check-cdc`.
+
+Examples for reference:
+
+* Help message
+
+```
+./cdc-start-up.sh --help
+```
+
+* Start Ignite node with specified properties:
+
+To start an Ignite cluster node, use `--ignite` or `-i` command with
`cdc-start-up.sh`. You also need to specify properties holder directory.
+
+There are currently 2 examples for 2 clusters, that you can run
simultaneously. You can find them under
`$IGNITE_HOME/examples/config/cdc-start-up/cluster-1` and
`$IGNITE_HOME/examples/config/cdc-start-up/cluster-2` as
`ignite-cdc.properties`. These files contains all independent settings that you
can tinker for your needs.
+
+NOTE: All properties files are preconfigured to work out of the box.
Review Comment:
Removed them
##########
docs/_docs/extensions-and-integrations/change-data-capture-extensions.adoc:
##########
@@ -339,3 +553,132 @@ Configuration is done via Ignite node plugin:
</bean>
</property>
```
+
+== Common CDC strategies
+
+There are basically two strategies to choose from when it comes to CDC
replication with Apache Ignite, and a handful of options to configure the
transport for the data.
+
+* Strategies include `Active-Passive` and `Active-Active` replication regimes.
You can read it as 'from one cluster to another only' and 'from one cluster to
another and vice versa'.
+
+The former strategy implies that only one cluster would be actively used for
data consumption from the outside user application, while the other one
consumes data through CDC.
+
+The latter approach allows users to use both cluster simultaneously, meanwhile
the CDC clients transfer the updates between them. For that strategy to work,
the user should configure conflict resolver.
+
+* To make things work you have two independent tools to configure:
+
+** Thin/Thick clients for connection to destination clusters - responsible for
'put' operations on the destination cluster.
+
+** Ignite/Kafka driven middleman data transport - You can pass data through
Kafka topics, or you can use Ignite out of the box solution.
+
+Basically, you can combine them any way you want to meet your project goals.
+
+=== CDC example manager
+
+`ignite-cdc-ext` ships with CDC example manager `cdc-start-up.sh` alongside
`kafka-to-ignite.sh`. You can find it under
'$IGNITE_HOME/examples/config/cdc-start-up/' directory.
+
+You can use this script to start all kinds of replication strategies without
any additional configuration.
+
+The script will use predefined configuration '.xml' files from
'$IGNITE_HOME/examples/config/cdc-start-up/' directory. Feel free to examine
them as you try the manager out.
+
+NOTE: Use `--help` to explore the manager capabilities
+
+NOTE: Please, enable `ignite-rest-http` and `ignite-json` to be able to run
`cdc-start-up.sh` with `--check-cdc`.
+
+Examples for reference:
+
+* Help message
+
+```
+./cdc-start-up.sh --help
+```
+
+* Start Ignite node with specified properties:
+
+To start an Ignite cluster node, use `--ignite` or `-i` command with
`cdc-start-up.sh`. You also need to specify properties holder directory.
+
+There are currently 2 examples for 2 clusters, that you can run
simultaneously. You can find them under
`$IGNITE_HOME/examples/config/cdc-start-up/cluster-1` and
`$IGNITE_HOME/examples/config/cdc-start-up/cluster-2` as
`ignite-cdc.properties`. These files contains all independent settings that you
can tinker for your needs.
Review Comment:
Fixed the typo
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@ignite.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
