AWS prescriptive-guidance documentation change
Summary
Updated documentation links, fixed formatting, corrected image paths, expanded SQS acronym, and reformatted important note about Saga pattern
Security assessment
Changes consist of documentation corrections, formatting improvements, and clarifications without introducing new security content or addressing specific vulnerabilities. The mention of security in the event sourcing/CQRS context remains unchanged from previous version.
Diff
diff --git a/prescriptive-guidance/latest/modernization-data-persistence/service-per-team.md b/prescriptive-guidance/latest/modernization-data-persistence/service-per-team.md index dc522a65e..644dea73f 100644 --- a//prescriptive-guidance/latest/modernization-data-persistence/service-per-team.md +++ b//prescriptive-guidance/latest/modernization-data-persistence/service-per-team.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Enabling data persistence in microservices](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Enabling data persistence in microservices](introduction.html) @@ -11 +11 @@ Amazon Kinesis Data Streams implementationAmazon EventBridge implementation -The event sourcing pattern is typically used with the [CQRS pattern](./cqrs-pattern.html) to decouple read from write workloads, and optimize for performance, scalability, and security. Data is stored as a series of events, instead of direct updates to data stores. Microservices replay events from an event store to compute the appropriate state of their own data stores. The pattern provides visibility for the current state of the application and additional context for how the application arrived at that state. The event sourcing pattern works effectively with the CQRS pattern because data can be reproduced for a specific event, even if the command and query data stores have different schemas. +The event sourcing pattern is typically used with the CQRS pattern to decouple read from write workloads, and optimize for performance, scalability, and security. Data is stored as a series of events, instead of direct updates to data stores. Microservices replay events from an event store to compute the appropriate state of their own data stores. The pattern provides visibility for the current state of the application and additional context for how the application arrived at that state. The event sourcing pattern works effectively with the CQRS pattern because data can be reproduced for a specific event, even if the command and query data stores have different schemas. @@ -13 +13 @@ The event sourcing pattern is typically used with the [CQRS pattern](./cqrs-patt -By choosing this pattern, you can identify and reconstruct the application’s state for any point in time. This produces a persistent audit trail and makes debugging easier. However, data becomes eventually consistent and this might not be appropriate for some use cases. +By choosing this pattern, you can identify and reconstruct the application's state for any point in time. This produces a persistent audit trail and makes debugging easier. However, data becomes eventually consistent and this might not be appropriate for some use cases. @@ -21 +21 @@ In the following illustration, Kinesis Data Streams is the main component of a c - + @@ -34 +34 @@ The workflow consists of the following steps: -The architecture in the following illustration uses EventBridge. EventBridge is a serverless service that uses events to connect application components, which makes it easier for you to build scalable, event-driven applications. Event-driven architecture is a style of building loosely coupled software systems that work together by emitting and responding to events. EventBridge provides a [default event bus](https://docs.aws.amazon.com//eventbridge/latest/userguide/create-event-bus.html) for events that are published by AWS services, and you can also create a [custom event bus](https://docs.aws.amazon.com//eventbridge/latest/userguide/create-event-bus.html) for domain-specific buses. +The architecture in the following illustration uses EventBridge. EventBridge is a serverless service that uses events to connect application components, which makes it easier for you to build scalable, event-driven applications. Event-driven architecture is a style of building loosely coupled software systems that work together by emitting and responding to events. EventBridge provides a [default event bus ](https://docs.aws.amazon.com/eventbridge/latest/userguide/create-event-bus.html)for events that are published by AWS services, and you can also create a [custom event bus](https://docs.aws.amazon.com/eventbridge/latest/userguide/create-event-bus.html) for domain-specific buses. @@ -36 +36 @@ The architecture in the following illustration uses EventBridge. EventBridge is - + @@ -50 +50 @@ The workflow consists of the following steps: - 6. Historical order events are sent to a new Amazon SQS queue (replay queue) for reprocessing, if required. + 6. Historical order events are sent to a new Amazon Simple Queue Service (Amazon SQS) queue (replay queue) for reprocessing, if required. @@ -72,3 +72 @@ You should consider using this pattern if: -###### Important - -If you use the event sourcing pattern, you must deploy the [Saga pattern](./saga-pattern.html) to maintain data consistency across microservices. +_**Important** : If you use the event sourcing pattern, you must deploy the Saga pattern to maintain data consistency across microservices._