AWS prescriptive-guidance documentation change
Summary
Updated documentation links, fixed quotation marks, adjusted image path references, and removed hyperlinks from pattern names
Security assessment
Changes involve structural/navigation updates (link paths, image references) and formatting fixes (quotation marks). No modifications to security-related content about IAM policies or data privacy mechanisms. No evidence of addressing vulnerabilities or security features.
Diff
diff --git a/prescriptive-guidance/latest/modernization-data-persistence/database-per-service.md b/prescriptive-guidance/latest/modernization-data-persistence/database-per-service.md index 0f53b6d7c..49838ae33 100644 --- a//prescriptive-guidance/latest/modernization-data-persistence/database-per-service.md +++ b//prescriptive-guidance/latest/modernization-data-persistence/database-per-service.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 @@ Loose coupling is the core characteristic of a microservices architecture, becau -In the following illustration, different AWS databases are used by the “Sales,” “Customer,” and “Compliance” microservices. These microservices are deployed as AWS Lambda functions and accessed through an Amazon API Gateway API. AWS Identity and Access Management (IAM) policies ensure that data is kept private and not shared among the microservices. Each microservice uses a database type that meets its individual requirements; for example, "Sales" uses Amazon Aurora, "Customer" uses Amazon DynamoDB, and "Compliance" uses Amazon Relational Database Service (Amazon RDS) for SQL Server. +In the following illustration, different AWS databases are used by the "Sales," "Customer," and "Compliance" microservices. These microservices are deployed as AWS Lambda functions and accessed through an Amazon API Gateway API. AWS Identity and Access Management (IAM) policies ensure that data is kept private and not shared among the microservices. Each microservice uses a database type that meets its individual requirements; for example, "Sales" uses Amazon Aurora, "Customer" uses Amazon DynamoDB, and "Compliance" uses Amazon Relational Database Service (Amazon RDS) for SQL Server. @@ -13 +13 @@ In the following illustration, different AWS databases are used by the “Sales, - + @@ -39 +39 @@ There are the following disadvantages to using the database-per-service pattern: -If you use the database-per-service pattern, you must deploy another pattern to implement queries that span multiple microservices. You can use the [API composition pattern](./api-composition.html) (which you can speed up with the [CQRS pattern](./cqrs-pattern.html)) or the [event sourcing pattern](./service-per-team.html) to create aggregated results. +If you use the database-per-service pattern, you must deploy another pattern to implement queries that span multiple microservices. You can use the API composition pattern (which you can speed up with the CQRS pattern) or the event sourcing pattern to create aggregated results.