@@ -186,19 +186,12 @@ <h1 class="page">Building Apps around the Event Mesh</h1>
186186< h1 id ="_architecture " class ="sect0 "> < a class ="anchor " href ="#_architecture "> </ a > < a class ="link " href ="#_architecture "> Architecture</ a > </ h1 >
187187< div class ="openblock partintro ">
188188< div class ="content ">
189- < div class ="paragraph ">
190- < p > The architecture of an event mesh-enabled system is a paradigm shift from
189+ The architecture of an event mesh-enabled system is a paradigm shift from
191190traditional transactional designs to an eventual consistency model. This design
192191aligns better with real-world processes, where different parts of a system may
193192operate asynchronously yet collaboratively. In this section, we explore the
194193technologies, flow, and structure that make the event mesh architecture
195- resilient, scalable, and developer-friendly.</ p >
196- </ div >
197- < div class ="paragraph ">
198- < p > The solution employs < em > Command Query Responsibility Segregation (CQRS)</ em > to
199- separate commands and queries. Commands are modeled as asynchronous events and
200- handled by the event mesh. Queries are synchronous operations safe to retry.</ p >
201- </ div >
194+ resilient, scalable, and developer-friendly.
202195</ div >
203196</ div >
204197< div class ="sect1 ">
@@ -253,37 +246,42 @@ <h2 id="in_depth"><a class="anchor" href="#in_depth"></a><a class="link" href="#
253246< div class ="sectionbody ">
254247< div class ="paragraph ">
255248< p > Building applications around the Event Mesh is a solution that can be applied
256- either to existing applications or to greenfield projects. The existing
257- applications can be divided by their domain boundaries. The divided parts might
258- become modules, or even external services. Those modules will issue commands,
259- directed towards the Event Mesh, which will be routed towards the configured
260- endpoints.</ p >
249+ both to existing and new projects. For existing applications, domain boundaries
250+ can guide the division into modular components, which may evolve into separate
251+ services. These modules will generate commands intended for the < em > Event Mesh</ em > ,
252+ which will then route these events to their designated endpoints. The < em > Event
253+ Mesh</ em > will allow for such transition, gradually making the system not only more
254+ responsive but also better suited to the real-world business logic.</ p >
261255</ div >
262256< div class ="sect2 ">
263257< h3 id ="_problem_analysis "> < a class ="anchor " href ="#_problem_analysis "> </ a > < a class ="link " href ="#_problem_analysis "> 2.1. Problem Analysis</ a > </ h3 >
264258< div class ="paragraph ">
265- < p > Traditional transactional systems enforce strict consistency, which slows
266- applications and distorts business logic. In our illustrative Cabs app example,
267- we must accommodate real-world scenarios, such as exiting a cab, even when
268- dependent systems (e.g., invoicing) encounter disruptions. Disregarding errors,
269- which preserve the integrity of existing data, discards the newly generated data
270- from genuine events. This results in a negative user experience and distorts
271- the actual business process, leading to potential customer dissatisfaction.</ p >
259+ < p > Traditional systems often enforce strict transactional consistency,
260+ which can impede application performance and compromise business logic.
261+ For instance, upon the completion of a ride-sharing service at the end-user’s
262+ destination, the system should reliably capture this real-world event, irrespective
263+ of any potential operational disruptions affecting dependent services (e.g.,
264+ invoicing).</ p >
265+ </ div >
266+ < div class ="paragraph ">
267+ < p > In such scenarios, transactional applications typically return an error, resulting
268+ in an adverse user experience and a deviation from the genuine business process,
269+ potentially leading to customer dissatisfaction.</ p >
272270</ div >
273271</ div >
274272< div class ="sect2 ">
275273< h3 id ="_solution_breakdown "> < a class ="anchor " href ="#_solution_breakdown "> </ a > < a class ="link " href ="#_solution_breakdown "> 2.2. Solution Breakdown</ a > </ h3 >
276274< div class ="paragraph ">
277- < p > The concept of employing the Event Mesh as a central, reliable hub for dispatching
278- commands, as events, lies at the heart of this solution. This approach aligns
279- closely with the Command Query Responsibility Segregation (CQRS) pattern, which
280- distinctly categorizes commands and queries. Commands, in this context, are
281- modeled as asynchronous events, designed to undergo processing by the event mesh.
282- On the other hand, queries are synchronous operations, safe to retry, ensuring
275+ < p > The concept of employing the < em > Event Mesh</ em > as a central, reliable hub for
276+ dispatching commands, as events, lies at the heart of this solution. This
277+ approach aligns closely with the Command Query Responsibility Segregation
278+ ( < em > CQRS </ em > ) pattern, which distinctly categorizes commands and queries. Commands,
279+ in this context, are modeled as asynchronous events, designed to undergo
280+ processing by the < em > Event Mesh </ em > . On the other hand, queries are synchronous operations, safe to retry, ensuring
283281no loss of data integrity due to transient errors.</ p >
284282</ div >
285283< div class ="paragraph ">
286- < p > The primary responsibility of the Event Mesh is twofold: firstly, it persists
284+ < p > The primary responsibility of the < em > Event Mesh</ em > is twofold: firstly, it persists
287285the incoming events, thereby maintaining a record of changes in the system’s
288286state. Secondly, it routes these events to their respective endpoints, ensuring
289287that the appropriate microservices are notified and can subsequently update
@@ -296,7 +294,7 @@ <h3 id="_solution_breakdown"><a class="anchor" href="#_solution_breakdown"></a><
296294the risk of data loss or system disruption due to transient issues.</ p >
297295</ div >
298296< div class ="paragraph ">
299- < p > By integrating the Event Mesh into the system architecture, several architectural
297+ < p > By integrating the < em > Event Mesh</ em > into the system architecture, several architectural
300298benefits are achieved:</ p >
301299</ div >
302300< div class ="ulist ">
@@ -310,7 +308,7 @@ <h3 id="_solution_breakdown"><a class="anchor" href="#_solution_breakdown"></a><
310308</ li >
311309< li >
312310< p > < strong > Correction of systemic issues</ strong > :
313- The Event Mesh’ s error-handling mechanism, through retries and event
311+ The < em > Event Mesh</ em > ' s error-handling mechanism, through retries and event
314312persistence, aids in minimizing the impact of failures on the end user.
315313This is crucial as it prevents bugs and outages from becoming visible to
316314the user, thereby preserving the system’s perceived responsiveness.</ p >
@@ -319,19 +317,19 @@ <h3 id="_solution_breakdown"><a class="anchor" href="#_solution_breakdown"></a><
319317< p > < strong > Enhanced system performance</ strong > :
320318The system becomes more responsive, as the end user no longer needs to
321319wait for multiple, often independent, operations to complete successfully.
322- The Event Mesh’ s event-driven model, coupled with the retries and event
320+ The < em > Event Mesh</ em > ' s event-driven model, coupled with the retries and event
323321persistence, ensures that critical state changes are propagated swiftly and
324322reliably, thereby improving the overall user experience.</ p >
325323</ li >
326324</ ul >
327325</ div >
328326</ div >
329327< div class ="sect2 ">
330- < h3 id ="_event_mesh_flow "> < a class ="anchor " href ="#_event_mesh_flow "> </ a > < a class ="link " href ="#_event_mesh_flow "> 2.3. Event Mesh Flow</ a > </ h3 >
328+ < h3 id ="_event_mesh_flow "> < a class ="anchor " href ="#_event_mesh_flow "> </ a > < a class ="link " href ="#_event_mesh_flow "> 2.3. < em > Event Mesh</ em > Flow</ a > </ h3 >
331329< div class ="ulist ">
332330< ul >
333331< li >
334- < p > Events are published as CloudEvents to a Knative’s Event Mesh.</ p >
332+ < p > Events are published as < em > Cloud Events </ em > to a < em > Knative</ em > 's < em > Event Mesh</ em > .</ p >
335333</ li >
336334< li >
337335< p > Triggers route events dynamically to the appropriate endpoints.</ p >
@@ -344,17 +342,14 @@ <h3 id="_event_mesh_flow"><a class="anchor" href="#_event_mesh_flow"></a><a clas
344342</ div >
345343< div class ="imageblock ">
346344< div class ="content ">
347- < img src ="https://www.plantuml.com/plantuml/svg/VP1DJiCm58JtFiMZ-rmWYwgqeHkeX2WNUBK7Ok4ubdyYzVQuZKbe5TZ5olTcFiqcHFOnTKOyn1OTIC8d0xPLdwBH5iBb_rfgnpRIwWMVBC_qwDoAED3ul4MUBKSzW9u6vES1eRsYMzz_mT-YZS-W3tJeLUwyOdlW23zeYJkK8vyuZ52p5O9bRk687uTYLgrB4zNqcav6XvPsR6GocTsZQ8d2L1aV3slQzVP3-uuKpCNgB1JkEwQpzI_FcjxoL5XgcUvdMioVL4soi-iuIOQcE5N259RYPgKYMNJ-3lfdkMPRqp7s7lJkjQFBvWihR61Lwimt " alt ="VP1DJiCm58JtFiMZ rmWYwgqeHkeX2WNUBK7Ok4ubdyYzVQuZKbe5TZ5olTcFiqcHFOnTKOyn1OTIC8d0xPLdwBH5iBb rfgnpRIwWMVBC qwDoAED3ul4MUBKSzW9u6vES1eRsYMzz mT YZS W3tJeLUwyOdlW23zeYJkK8vyuZ52p5O9bRk687uTYLgrB4zNqcav6XvPsR6GocTsZQ8d2L1aV3slQzVP3 uuKpCNgB1JkEwQpzI FcjxoL5XgcUvdMioVL4soi iuIOQcE5N259RYPgKYMNJ 3lfdkMPRqp7s7lJkjQFBvWihR61Lwimt " width ="100% ">
345+ < img src ="https://www.plantuml.com/plantuml/svg/XPBHhjGW48RlUOgnzzi7wCNcsDGOeySOZG_0qkcMB8NA33MDyTsbb6CNNUCT_FF_tv0PdeYbvp0PyOf7d10coUYrFBd0HbiKTDDsbbvEi5rvdH5cPzPK4yguq4FrPa7By8mqLl1302WtpSvkMlNUIjOBGklT3Nq5al8nshu531WjShZ9L4adyLE8mPaUFLJFMda7X7xH2kalUESZsXDysGs9aRKiHNylMLuauM7lsdjdrvRGTtPnMcbxBR2xYe-mHo23i_TFy4V7Uj1AidQsODyNihuDuIxw0QzIhK0hCKxb68xgwtbEkFrQF34xkbt8Wsgt9hbowjrtUphdtJJmALoCfX5msoozk6glhoFNvvY51hxEiG6cBcBF7OQqIOWSzAI9NpZbSg0sE73zpwuPUehlAeCDV7Q1yO4lZ_w_ldBafVdnK-lpyM4QU8jCeEtWG5vY2lgz98h-ANNyXjyJomfuLCxt99xGzc4olm00 " alt ="XPBHhjGW48RlUOgnzzi7wCNcsDGOeySOZG 0qkcMB8NA33MDyTsbb6CNNUCT FF tv0PdeYbvp0PyOf7d10coUYrFBd0HbiKTDDsbbvEi5rvdH5cPzPK4yguq4FrPa7By8mqLl1302WtpSvkMlNUIjOBGklT3Nq5al8nshu531WjShZ9L4adyLE8mPaUFLJFMda7X7xH2kalUESZsXDysGs9aRKiHNylMLuauM7lsdjdrvRGTtPnMcbxBR2xYe mHo23i TFy4V7Uj1AidQsODyNihuDuIxw0QzIhK0hCKxb68xgwtbEkFrQF34xkbt8Wsgt9hbowjrtUphdtJJmALoCfX5msoozk6glhoFNvvY51hxEiG6cBcBF7OQqIOWSzAI9NpZbSg0sE73zpwuPUehlAeCDV7Q1yO4lZ w ldBafVdnK lpyM4QU8jCeEtWG5vY2lgz98h ANNyXjyJomfuLCxt99xGzc4olm00 " width ="100% ">
348346</ div >
349347</ div >
350- < div class ="paragraph ">
351- < p > The diagram illustrates the flow of events between the legacy application, the Knative Event Mesh, the fee calculator service, and the datastore.</ p >
352- </ div >
353348</ div >
354349< div class ="sect2 ">
355350< h3 id ="_supporting_legacy_systems "> < a class ="anchor " href ="#_supporting_legacy_systems "> </ a > < a class ="link " href ="#_supporting_legacy_systems "> 2.4. Supporting Legacy Systems</ a > </ h3 >
356351< div class ="paragraph ">
357- < p > One of the strengths of an event mesh architecture is its ability to integrate seamlessly with legacy systems, making them more resilient and adaptable. Legacy applications can be retrofitted to produce and consume events through lightweight adapters. For instance:</ p >
352+ < p > One of the strengths of an < em > Event Mesh </ em > architecture is its ability to integrate seamlessly with legacy systems, making them more resilient and adaptable. Legacy applications can be retrofitted to produce and consume events through lightweight adapters. For instance:</ p >
358353</ div >
359354< div class ="ulist ">
360355< ul >
@@ -379,7 +374,7 @@ <h3 id="_improving_resilience_in_traditional_applications"><a class="anchor" hre
379374< p > For example, invoicing and notification services in an e-commerce platform can process OrderPlaced events independently, ensuring that downtime in one service does not block the entire order workflow.</ p >
380375</ div >
381376< div class ="paragraph ">
382- < p > Retry mechanisms provided by the event mesh guarantee that transient failures are handled gracefully without data loss.</ p >
377+ < p > Retry mechanisms provided by the < em > Event Mesh </ em > guarantee that transient failures are handled gracefully without data loss.</ p >
383378</ div >
384379</ div >
385380</ div >
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&size=40){kind=avatar}
0 commit comments