[CI] Publish Documentation for 1684084 - 1684084 🚀

sitemap.xml

@@ -2,38 +2,38 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-pattern-modernization-cdc/solution-pattern-modernization-cdc/01-pattern.html</loc>
-<lastmod>2023-02-01T10:00:44.844Z</lastmod>
+<lastmod>2023-06-06T08:54:26.999Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-pattern-modernization-cdc/solution-pattern-modernization-cdc/02-architecture.html</loc>
-<lastmod>2023-02-01T10:00:44.844Z</lastmod>
+<lastmod>2023-06-06T08:54:26.999Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-pattern-modernization-cdc/solution-pattern-modernization-cdc/03-demo.html</loc>
-<lastmod>2023-02-01T10:00:44.844Z</lastmod>
+<lastmod>2023-06-06T08:54:26.999Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-pattern-modernization-cdc/solution-pattern-modernization-cdc/04-devresources.html</loc>
-<lastmod>2023-02-01T10:00:44.844Z</lastmod>
+<lastmod>2023-06-06T08:54:26.999Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-pattern-modernization-cdc/solution-pattern-modernization-cdc/appendix-a.html</loc>
-<lastmod>2023-02-01T10:00:44.844Z</lastmod>
+<lastmod>2023-06-06T08:54:26.999Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-pattern-modernization-cdc/solution-pattern-modernization-cdc/content-overview.html</loc>
-<lastmod>2023-02-01T10:00:44.844Z</lastmod>
+<lastmod>2023-06-06T08:54:26.999Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-pattern-modernization-cdc/solution-pattern-modernization-cdc/index.html</loc>
-<lastmod>2023-02-01T10:00:44.844Z</lastmod>
+<lastmod>2023-06-06T08:54:26.999Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-pattern-modernization-cdc/solution-pattern-modernization-cdc/single-page-pre.html</loc>
-<lastmod>2023-02-01T10:00:44.844Z</lastmod>
+<lastmod>2023-06-06T08:54:26.999Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-pattern-modernization-cdc/solution-pattern-modernization-cdc/single-page.html</loc>
-<lastmod>2023-02-01T10:00:44.844Z</lastmod>
+<lastmod>2023-06-06T08:54:26.999Z</lastmod>
 </url>
 </urlset>

solution-pattern-modernization-cdc/01-pattern.html

@@ -278,7 +278,7 @@ <h2 id="background"><a class="anchor" href="#background"></a>The story behind th
 <h2 id="_solution"><a class="anchor" href="#_solution"></a>Technical overview</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>This solution pattern builds on top an event-driven architecture in order to support the extension of the legacy stack. The architecture includes new microservices, event streaming, event processing and search indexing tools.</p>
+<p>This solution pattern builds on top of an event-driven architecture in order to support the extension of the legacy stack. The architecture includes new microservices, event streaming, event processing and search indexing tools.</p>
 </div>
 <div class="paragraph">
 <p>In respect to the <a href="#_story_goals">story goals</a> and <a href="#use-cases">targeted use cases</a>, it&#8217;s recommended to consider adopting an <a href="https://www.enterpriseintegrationpatterns.com/">Enterprise Integration Pattern</a> for data integration, more specifically, adopting the <a href="https://www.redhat.com/en/topics/integration/what-is-change-data-capture">Change Data Capture (CDC)</a> pattern.</p>

solution-pattern-modernization-cdc/02-architecture.html

@@ -264,7 +264,7 @@ <h3 id="_the_need_to_store_data_in_multiple_data_stores"><a class="anchor" href=
 </div>
 </div>
 <div class="paragraph">
-<p>One could think about changing the service to push the data not only to its own database, but also to elasticsearch. It becomes a distributed system where the core data operations are no longer handled in single transactions. Be aware: this is yet another anti-pattern, called <a href="https://developers.redhat.com/articles/2021/07/30/avoiding-dual-writes-event-driven-applications">dual write</a>.</p>
+<p>One could think about changing the service to push the data not only to its own database, but also to ElasticSearch. It becomes a distributed system where the core data operations are no longer handled in single transactions. Be aware: this is yet another anti-pattern, called <a href="https://developers.redhat.com/articles/2021/07/30/avoiding-dual-writes-event-driven-applications">dual write</a>.</p>
 </div>
 <div class="admonitionblock important">
 <table>
@@ -408,7 +408,7 @@ <h3 id="scenario-cashback-wallet"><a class="anchor" href="#scenario-cashback-wal
 </div>
 </li>
 <li>
-<p>Next, <a href="https://debezium.io">Debezium</a> streams the data them over to Kafka. The event streaming solution can be hosted on-premise or on the cloud. In this implementation, we are using <a href="https://red.ht/TryKafka">Red Hat Managed OpenShift Streams for Apache Kafka</a>.</p>
+<p>Next, <a href="https://debezium.io">Debezium</a> streams the data them over to Kafka. The event streaming solution can be hosted on-premise or on the cloud. In this implementation, we are using <a href="https://www.redhat.com/en/resources/amq-streams-datasheet">AMQ Streams</a>, Red Hat&#8217;s Kubernetes-native Apache Kafka distribution.</p>
 </li>
 <li>
 <p>An integration microservice, <code>sales-streams</code>, reacts to events captured by Debezium and published on three topics, respective to <code>sale-change-event</code> and <code>lineitem-change-event</code>.</p>