[CI] Publish Preview for PR #1 05852c2

Author: github-actions[bot]

pull-1/sitemap.xml

@@ -2,22 +2,22 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-patterns/solution-pattern-event-mesh-for-microservices/01-pattern.html</loc>
-<lastmod>2025-03-26T18:22:49.683Z</lastmod>
+<lastmod>2025-03-27T19:54:07.209Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-patterns/solution-pattern-event-mesh-for-microservices/02-architecture.html</loc>
-<lastmod>2025-03-26T18:22:49.683Z</lastmod>
+<lastmod>2025-03-27T19:54:07.209Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-patterns/solution-pattern-event-mesh-for-microservices/03-demo.html</loc>
-<lastmod>2025-03-26T18:22:49.683Z</lastmod>
+<lastmod>2025-03-27T19:54:07.209Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-patterns/solution-pattern-event-mesh-for-microservices/developer-resources.html</loc>
-<lastmod>2025-03-26T18:22:49.683Z</lastmod>
+<lastmod>2025-03-27T19:54:07.209Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-patterns/solution-pattern-event-mesh-for-microservices/index.html</loc>
-<lastmod>2025-03-26T18:22:49.683Z</lastmod>
+<lastmod>2025-03-27T19:54:07.209Z</lastmod>
 </url>
 </urlset>

pull-1/solution-pattern-event-mesh-for-microservices/02-architecture.html

@@ -293,7 +293,8 @@ <h3 id="_event_mesh_flow"><a class="anchor" href="#_event_mesh_flow"></a><a clas
 <div class="olist arabic">
 <ol class="arabic">
 <li>
-<p>An end-user application sends an <em>HTTP</em> request to the <em>Event Mesh</em>. Such message can be understood as a <em>Command</em> type event.</p>
+<p>An end-user application sends an <em>HTTP</em> request to the <em>Event Mesh</em>.
+Such message can be understood as a <em>Command</em> type event.</p>
 </li>
 <li>
 <p>The <em>Event Mesh</em> (Broker) persists the event in a queue (like an Apache Kafka topic, but the implementation is hidden from the user).

pull-1/solution-pattern-event-mesh-for-microservices/03-demo.html

@@ -156,7 +156,7 @@ <h2 id="_demonstration"><a class="anchor" href="#_demonstration"></a><a class="l
 <div class="sectionbody">
 <div class="paragraph">
 <p>Let&#8217;s take a look at the following example.
-We&#8217;ll be looking at a Cabs ride-sharing application, that mimics real-world solutions of similar kind.
+We&#8217;ll be looking at a Cabs ride-sharing application, that resembles real-world solutions of similar kind.
 The application is written in a popular Java framework.</p>
 </div>
 <div class="sect2">
@@ -189,18 +189,19 @@ <h3 id="_initial_application"><a class="anchor" href="#_initial_application"></a
     }
     Address from = addressRepository.getByHash(transitDetails.from.getHash());
     Address to = addressRepository.getByHash(destinationAddress.getHash());
+
     Money finalPrice = completeTransitService.completeTransit(
       driverId, requestUUID, from, to); <i class="conum" data-value="2"></i><b>(2)</b>
-    Money driverFee = driverFeeService.calculateDriverFee(
-      finalPrice, driverId);
+    Money driverFee = driverFeeService.calculateDriverFee(finalPrice, driverId);
     driverService.markNotOccupied(driverId); <i class="conum" data-value="2"></i><b>(2)</b>
-    transitDetailsFacade.transitCompleted(requestUUID,
-      Instant.now(clock), finalPrice, driverFee); <i class="conum" data-value="2"></i><b>(2)</b>
-    awardsService.registerMiles(transitDetails.client.getId(),
-      transitDetails.transitId); <i class="conum" data-value="2"></i><b>(2)</b>
+
+    transitDetailsFacade.transitCompleted(requestUUID, Instant.now(clock),
+      finalPrice, driverFee); <i class="conum" data-value="2"></i><b>(2)</b>
+    awardsService.registerMiles(transitDetails.client.getId(), transitDetails.transitId); <i class="conum" data-value="2"></i><b>(2)</b>
     invoiceGenerator.generate(finalPrice.toInt(),
       transitDetails.client.getName() + " " +
       transitDetails.client.getLastName()); <i class="conum" data-value="2"></i><b>(2)</b>
+
     eventsEventSender.publish(new TransitCompleted(
       transitDetails.client.getId(), transitDetails.transitId,
       transitDetails.from.getHash(), destinationAddress.getHash(),
@@ -309,19 +310,22 @@ <h4 id="_drivers_module"><a class="anchor" href="#_drivers_module"></a><a class=
 <div class="content">
 <pre class="highlightjs highlight"><code class="language-rust hljs" data-lang="rust">impl Service {
   pub async fn calculate_fee(&amp;mut self, ce: Event) -&gt; Result&lt;()&gt; {
-    let fee_event = Self::parse_fee_event(ce)?; <i class="conum" data-value="1"></i><b>(1)</b>
-    let subject = fee_event.id.clone();
+    let calc_fee_intent = Self::unwrap_calculatefee(ce)?; <i class="conum" data-value="1"></i><b>(1)</b>
+    let subject = calc_fee_intent.id.clone();
+
+    log::debug!("calculate fee for: {:?}", calc_fee_intent);
+    let drv = self.repo.get(&amp;calc_fee_intent.entity.driver_id).await?;
 
-    let drv = self.repo.get(&amp;fee_event.entity.driver_id).await?;
+    let fee = drv.calculate_fee(&amp;calc_fee_intent.entity.transit_price); <i class="conum" data-value="2"></i><b>(2)</b>
 
-    let fee = drv.calculate_fee(&amp;fee_event.entity.transit_price); <i class="conum" data-value="2"></i><b>(2)</b>
+    log::debug!("fee value: {:?}", fee);
 
-    let fee_event = DriverFeeEvent {
-        driver_id: fee_event.entity.driver_id,
+    let driverfee_event = DriverFeeEvent {
+        driver_id: calc_fee_intent.entity.driver_id,
         fee,
     }; <i class="conum" data-value="3"></i><b>(3)</b>
 
-    let mut builder = fee_event.to_builder(); <i class="conum" data-value="3"></i><b>(3)</b>
+    let mut builder = driverfee_event.to_builder(); <i class="conum" data-value="3"></i><b>(3)</b>
     if let Some(id) = subject {
         builder = builder.subject(id);
     } <i class="conum" data-value="3"></i><b>(3)</b>
@@ -342,19 +346,19 @@ <h4 id="_drivers_module"><a class="anchor" href="#_drivers_module"></a><a class=
 <table>
 <tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
-<td>We are parsing the internal, business logic, fee event from the <em>Cloud Events</em> envelope.</td>
+<td>We are unwrapping <em>Cloud Event</em> envelope into an internal, domain, fee value object.</td>
 </tr>
 <tr>
 <td><i class="conum" data-value="2"></i><b>2</b></td>
-<td>We are calculating the fee for this event, using some business logic.</td>
+<td>We are calculating the fee value using some domain logic.</td>
 </tr>
 <tr>
 <td><i class="conum" data-value="3"></i><b>3</b></td>
-<td>We are wrapping the calculated fee into the <em>Cloud Events</em> envelope.</td>
+<td>We are wrapping the calculated fee value into a new <em>Cloud Event</em>.</td>
 </tr>
 <tr>
 <td><i class="conum" data-value="4"></i><b>4</b></td>
-<td>We are sending the fee back to the <em>Event Mesh</em> using <em>HTTP REST</em> client.</td>
+<td>We are sending the fee, as <em>Cloud Event</em>, back to the <em>Event Mesh</em> using <em>HTTP REST</em> client.</td>
 </tr>
 </table>
 </div>
@@ -489,7 +493,7 @@ <h4 id="_event_mesh"><a class="anchor" href="#_event_mesh"></a><a class="link" h
 </td>
 <td class="content">
 <div class="paragraph">
-<p>The policy is <code>exponential</code>, and the <code>retry</code> is 10, which means that after approximately 6 min and 50 sec the event will be dropped.</p>
+<p>In our example, the policy is <code>exponential</code>, and the <code>retry</code> is 10, which means that after approximately 6 min and 50 sec the event will be dropped (or routed to the <code>deadLetterSink</code> if configured).</p>
 </div>
 </td>
 </tr>
@@ -504,7 +508,7 @@ <h4 id="_event_mesh"><a class="anchor" href="#_event_mesh"></a><a class="link" h
 <td class="content">
 <div class="paragraph">
 <p>A <code>deadLetterSink</code> option could be configured for the <em>Broker</em> to send the events that failed to be delivered in time to a back-up location.
-Events captured in a back-up location can be re-transmitted into the <em>Event Mesh</em> later.</p>
+Events captured in a back-up location can be re-transmitted into the <em>Event Mesh</em> later by reconfiguring the <em>Mesh</em> (after resolving the outage or deploying a bug fix).</p>
 </div>
 </td>
 </tr>
@@ -555,7 +559,7 @@ <h4 id="_legacy_application_changes"><a class="anchor" href="#_legacy_applicatio
 </tr>
 <tr>
 <td><i class="conum" data-value="2"></i><b>2</b></td>
-<td>We are using the <code>@EventListener</code> annotation to listen for the business events withing the applition.
+<td>We are using the <code>@EventListener</code> annotation to listen for the domain events within the application.
 Don&#8217;t confuse this with <em>Cloud Events</em> that are sent and received outside the application.</td>
 </tr>
 <tr>
@@ -569,7 +573,7 @@ <h4 id="_legacy_application_changes"><a class="anchor" href="#_legacy_applicatio
 </table>
 </div>
 <div class="paragraph">
-<p>To make it work, we need to add a new <em>Cloud Event</em> sender and listener.
+<p>To communicate with the <em>Event Mesh</em>, we need to add a new <em>Cloud Event</em> sender and listener.
 That&#8217;s being done similarly, as in the case of <em>Rust</em> application.</p>
 </div>
 <div class="paragraph">
@@ -686,12 +690,12 @@ <h4 id="_legacy_application_changes"><a class="anchor" href="#_legacy_applicatio
 <table>
 <tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
-<td>We unwrap the <em>CloudEvent</em> into our custom event type</td>
+<td>We unwrap the <em>CloudEvent</em> into our domain event type (in the example that&#8217;s the <code>DriverFeeCalculated</code> type)</td>
 </tr>
 <tr>
 <td><i class="conum" data-value="2"></i><b>2</b></td>
 <td>And publish it withing the application, using the framework&#8217;s <em>EventsPublisher</em> implementation.
-The event will be transmitted to the methods annotated with <code>@EventListener</code>.</td>
+The domain events will be transmitted to the methods annotated with <code>@EventListener</code>.</td>
 </tr>
 </table>
 </div>
@@ -703,7 +707,7 @@ <h4 id="_legacy_application_changes"><a class="anchor" href="#_legacy_applicatio
 </td>
 <td class="content">
 <div class="paragraph">
-<p>Don&#8217;t confuse the the framework&#8217;s <em>EventsPublisher</em> with <em>Cloud Event</em> sender and receiver.</p>
+<p>Don&#8217;t confuse the framework&#8217;s <em>EventsPublisher</em> with <em>Cloud Event</em> sender and receiver.</p>
 </div>
 </td>
 </tr>
@@ -1117,7 +1121,8 @@ <h4 id="_configuring_the_event_mesh"><a class="anchor" href="#_configuring_the_e
 </div>
 <div class="paragraph">
 <p>The console shows two sink bindings on the left, and they are feeding the events from the applications to the <em>Broker</em> (depicted in the center).
-on the right, you could see the two applications deployed as <em>Knative</em> services, and two triggers (as lines) that configure the <em>Event Mesh</em> to feed appropriate events to the applications.</p>
+The <em>Broker</em> is the centralized infrastructure piece that ensures a proper decoupling of the services.
+On the right, you could see the two applications deployed as <em>Knative</em> services, and two triggers (as lines) that configure the <em>Event Mesh</em> to feed appropriate events to the applications.</p>
 </div>
 </div>
 </div>

pull-1/solution-pattern-event-mesh-for-microservices/developer-resources.html

@@ -155,10 +155,10 @@ <h2 id="_developer_resources"><a class="anchor" href="#_developer_resources"></a
 <div class="ulist">
 <ul>
 <li>
-<p><a href="https://github.com/cardil/cabs-usvc">Demo Source</a> <em>(The example code used in this solution)</em></p>
+<p><a href="https://github.com/cardil/cabs-usvc">Demo source code</a> &mdash; <em>The example code used in this solution, based on the <a href="https://github.com/legacyfighter/cabs-java">LegacyFighter Java app</a></em></p>
 </li>
 <li>
-<p><a href="https://youtu.be/Rc5IO6S6ZOk">youtu.be / Rc5IO6S6ZOk</a> <em>(The talk that served a base for this solution)</em></p>
+<p><a href="https://youtu.be/Rc5IO6S6ZOk">Let&#8217;s get meshy! Microservices are easy with Event Mesh</a> &mdash; <em>The talk that served a base for this solution</em></p>
 </li>
 <li>
 <p><a href="https://www.redhat.com/en/technologies/cloud-computing/openshift/serverless">Red Hat OpenShift Serverless</a></p>