@@ -23,7 +23,7 @@ Then we filter out only the events we need and publish them in the queue
2323
2424### Event publishing
2525
26- NATS Streaming is used as a message broker.
26+ NATS JetStream is used as a message broker.
2727Service publishes the following structure.
2828The name of the topic for subscription to receive messages is formed from the prefix of the topic,
2929the name of the database and the name of the table ` prefix + schema_table ` .
@@ -39,7 +39,7 @@ the name of the database and the name of the table `prefix + schema_table`.
3939}
4040```
4141
42- Messages are published to Nats-Streaming at least once!
42+ Messages are published to NATS (JetStream) at least once!
4343
4444### Filter configuration example
4545
@@ -56,7 +56,7 @@ This filter means that we only process events occurring with the `users` table,
5656and in particular ` insert ` and ` update ` data.
5757
5858### Topic mapping
59- By default, output NATS topic name consist of prefix, DB schema, and DB table name,
59+ By default, output NATS topic name consist of prefix, DB schema, and DB table name,
6060but if you want to send all update in one topic you should be configured the topic map:
6161``` yaml
6262 topicsMap :
@@ -114,5 +114,5 @@ monitoring:
114114You can start the container from the project folder (configuration file is required)
115115
116116` ` `
117- docker run -v $(pwd)/config.yml:/app/config.yml ihippik/wal-listener:v2.0 .0
117+ docker run -v $(pwd)/config.yml:/app/config.yml ihippik/wal-listener:v2.1 .0
118118```
0 commit comments