Content for the solution pattern

dev-site.yml

@@ -4,16 +4,14 @@ runtime:
 site:
   title: Solution Patterns for Cloud Native Architectures (Dev Mode)  
   url: http://localhost:3000/
-  start_page: solution-pattern-template::index.adoc
+  start_page: solution-pattern-event-mesh-for-microservices::index.adoc
 
 content:
   sources:
     - url: .
       branches: HEAD
       start_path: documentation
 asciidoc:
-  attributes:
-    title: Red Hat Solution Patterns (Dev Mode)
   extensions:
     - ./lib/remote-include-processor.js
     - ./lib/tab-block.js

documentation/antora.yml

@@ -1,5 +1,5 @@
-name: solution-pattern-template
-title: Template Tutorial
+name: solution-pattern-event-mesh-for-microservices
+title: Event Mesh For Applications 
 version: master
 nav:
   - modules/ROOT/nav.adoc

documentation/modules/ROOT/nav.adoc

@@ -9,17 +9,8 @@
 ** xref:02-architecture.adoc#more_tech[{module}.{counter:submodule2}. More about the technology stack]
 
 * xref:03-demo.adoc[{counter:module}. See the Solution in Action]
-** xref:03-demo.adoc#_demonstration[{module}.{counter:submodule3}. Demonstration]
+** xref:03-demo.adoc#_initial_application[{module}.{counter:submodule3}. Initial application]
 ** xref:03-demo.adoc#_run_the_demonstration[{module}.{counter:submodule3}. Run this demonstration]
-*** xref:03-demo.adoc#_before_getting_started[{module}.{counter:submodule3}. Pre-requisites]
-*** xref:03-demo.adoc#_installing_the_demo[{module}.{counter:submodule3}. Installing the demo]
-*** xref:03-demo.adoc#_walkthrough_guide[{module}.{counter:submodule3}. Walkthrough guide]
-
-* xref:04-workshop.adoc[{counter:module}. Workshop]
-** xref:04-workshop.adoc#_installing_the_workshop_environment[{module}.{counter:submodule4}. Installing the workshop environment]
-*** xref:04-workshop.adoc#_before_getting_started[{module}.{counter:submodule4}. Pre-requisites]
-*** xref:04-workshop.adoc#_installing_the_environment[{module}.{counter:submodule4}. Installing the environment]
-** xref:04-workshop.adoc#deliver_wksp[{module}.{counter:submodule4}. Delivering the workshop]
 
 * xref:developer-resources.adoc[{counter:module}. Developer Resources]
 

documentation/modules/ROOT/pages/01-pattern.adoc

@@ -1,7 +1,28 @@
 == The story behind this solution pattern
 
-A description of the story that was used to build the demo and architectures of this SP.
+Cabs is a fictional transportation company.
+Engineers at Cabs were struggling with their transactional-style, monolith application.
+They recently started an effort to modernize it.
+
+The team saw a https://www.youtube.com/watch?v=Rc5IO6S6ZOk[talk on _Event Mesh_].
+The talk presented the advantages of moving beyond transactional architectures in favor of eventual consistency.
+By leveraging event meshes with technologies like Knative, developers can achieve decoupled, reliable microservices without extensive re-engineering.
+This solution addresses inefficiencies and aligns distributed systems with real-world business processes.
+The team had figured out they could leverage the _CQRS_ pattern together with _Knative's Event Mesh_
+to modernize their application in a non-extrusive way.
 
 == The Solution
 
-This is a summary of the solution
+The core of this solution is an event mesh—a dynamic, flexible layer that routes, retries, and processes asynchronous events across distributed components.
+Using _Knative Eventing_ and _CloudEvents_, this pattern enables:
+
+- *Reliable delivery* of events with retry mechanisms.
+- Simplified *asynchronous workflows*.
+- *Decoupling* of services to improve scalability, testability and resilience.
+
+The approach of Cabs engineering team is to extract well-defined services, using the _CQRS_ pattern to identify _Commands_ from _Queries_, and model the
+_Commands_ as _Events_.
+Those events will be routed to the _Event Mesh_ with regular _HTTP_ messages.
+The _CloudEvents_ library ensures the proper serialization of the events to and from the _HTTP_ messages.
+The _Event Mesh_
+will handle not only the persistence of the events in-flight, but also all the required logic of retry in case of endpoint failure.