Arch

Author: cardil

documentation/modules/ROOT/pages/02-architecture.adoc

@@ -5,34 +5,64 @@
 
 = Architecture 
 
-Introduction for the architecture of this solution pattern.
+The architecture of an event mesh-enabled system is a paradigm shift from 
+traditional transactional designs to an eventual consistency model. This design
+aligns better with real-world processes, where different parts of a system may
+operate asynchronously yet collaboratively. In this section, we explore the
+technologies, flow, and structure that make the event mesh architecture
+resilient, scalable, and developer-friendly.
+
+The solution employs _Command Query Responsibility Segregation (CQRS)_ to
+separate commands and queries. Commands are modeled as asynchronous events and
+handled by the event mesh. Queries are synchronous operations safe to retry.
 
 [#tech_stack]
 == Technology Stack
 
+Here's the list of technologies used in this solution and its examples:
 
-The solution employs Command Query Responsibility Segregation (CQRS) to separate commands and queries:
+* Red Hat supported products
+** https://www.redhat.com/en/technologies/cloud-computing/openshift[Red Hat OpenShift]
+   — Orchestrate containerized applications. Based on https://kubernetes.io/[Kuberentes].
+** https://www.redhat.com/en/technologies/cloud-computing/openshift/serverless[Red Hat OpenShift Serverless]
+   — Provides the _Event Mesh_ and _Serverless_ capabilities. Based on https://knative.dev[Knative].
+** https://swc.saas.ibm.com/en-us/redhat-marketplace/products/red-hat-amq[Red Hat AMQ Streams]
+   — (Optional) Provides a persistence for _Event Mesh_, likely needed in production. Based on https://strimzi.io/[Strimzi].
+* Other open source technologies:
+** https://cloudevents.io/[CloudEvents] — Provides a standard for event metadata
+** Rust and https://access.redhat.com/products/quarkus[Quarkus] — Implementation examples.
+** https://opentelemetry.io/[OpenTelemetry] — (Optional) Facilitates tracing for observability.
 
-Commands are modeled as asynchronous events and handled by the event mesh.
+[#in_depth]
+== An in-depth look at the solution's architecture
 
-Queries are synchronous operations safe to retry.
+////
+Technical description including all or some of the following: architecture ired diagrams. In-depth details of the decisions made and solutions used. Description of each service and what it is used for. Description of any integration.
+////
 
+=== Problem Analysis
 
+Traditional transactional systems enforce strict consistency, which slows 
+applications and distorts business logic. In our example, Cabs app, must
+account for a real-life events like exiting a cab, even if dependent systems
+(e.g. invoicing) experience downtime. Throwing errors, while keeps the
+consistency in already stored data, loses the new data from real life events.
+This leads to a bad impression by the end-users, and distorts the actual
+business process.
 
-* Red Hat supported products
-** https://www.redhat.com/en/technologies/cloud-computing/openshift[Red Hat OpenShift]
-** Red Hat Application Foundation
-*** https://access.redhat.com/products/quarkus[Quarkus]
-*** https://www.redhat.com/en/technologies/cloud-computing/openshift/openshift-streams-for-apache-kafka[Kafka Streams]
-* Other open source products:
-** https://www.postgresql.org/[PostgreSQL database]
-** https://helm.sh/[Helm]
+=== Solution Breakdown
 
+Split services into independently operating microservices with distinct responsibilities.
 
-[#in_depth]
-== An in-depth look at the solution's architecture
+Utilize CQRS to separate commands (asynchronous state changes) from queries (synchronous, retry-safe reads).
+
+=== Event Mesh Flow
+
+Events like CompleteTransit are published as CloudEvents to a Knative broker.
+
+Triggers route events dynamically to the appropriate microservices.
 
-Technical description including all or some of the following: architecture ir ed diagrams. In-depth details of the decisions made and solutions used. Description of each service and what it is used for. Description of any integration.
+Services process events, update state, and emit new events for downstream consumers.
 
 === Using images