AWS prescriptive-guidance documentation change
Summary
Updated documentation links, fixed apostrophes in text, removed redundant section header, and adjusted hyperlink formatting
Security assessment
Changes focus on formatting consistency (apostrophes, link structure) and content organization. Security-related statements about IAM policies and data privacy remain unchanged. No introduction or modification of security controls or vulnerability disclosures.
Diff
diff --git a/prescriptive-guidance/latest/modernization-data-persistence/faq.md b/prescriptive-guidance/latest/modernization-data-persistence/faq.md index 6c0bb1fc2..b1b488042 100644 --- a//prescriptive-guidance/latest/modernization-data-persistence/faq.md +++ b//prescriptive-guidance/latest/modernization-data-persistence/faq.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) @@ -7 +7 @@ -When can I modernize my monolithic database as part of my modernization journey?Can I keep a legacy monolithic database for multiple microservices?What should I consider when designing databases for a microservices architecture?What is a common pattern for maintaining data consistency across different microservices?How do I maintain transaction automation?Do I have to use a separate database for each microservice?How can I keep a microservice’s persistent data private if they all share a single database? +When can I modernize my monolithic database as part of my modernization journey?Can I keep a legacy monolithic database for multiple microservices?What should I consider when designing databases for a microservices architecture?What is a common pattern for maintaining data consistency across different microservices?How do I maintain transaction automation?Do I have to use a separate database for each microservice?How can I keep a microservice's persistent data private if they all share a single database? @@ -11,2 +10,0 @@ When can I modernize my monolithic database as part of my modernization journey? -This section provides answers to commonly raised questions about enabling data persistence in microservices. - @@ -23 +21 @@ Keeping a shared monolithic database for multiple microservices creates tight co -You should design your application based on domains that align with your application’s functionality. Make sure that you evaluate the application’s functionality and decide if it requires a relational database schema. You should also consider using a NoSQL database, if it fits your requirements. +You should design your application based on domains that align with your application's functionality. Make sure that you evaluate the application's functionality and decide if it requires a relational database schema. You should also consider using a NoSQL database, if it fits your requirements. @@ -27 +25 @@ You should design your application based on domains that align with your applica -The most common pattern is using an [event-driven architecture](https://aws.amazon.com//event-driven-architecture/). +The most common pattern is using an [event-driven architecture](https://aws.amazon.com/event-driven-architecture/). @@ -31 +29 @@ The most common pattern is using an [event-driven architecture](https://aws.amaz -In a microservices architecture, a transaction consists of multiple local transactions handled by different microservices. If a local transaction fails, you need to roll back the successful transactions that were previously completed. You can use the [Saga pattern](./saga-pattern.html) to avoid this. +In a microservices architecture, a transaction consists of multiple local transactions handled by different microservices. If a local transaction fails, you need to roll back the successful transactions that were previously completed. You can use the [saga pattern](./saga-pattern.html) to avoid this. @@ -35 +33 @@ In a microservices architecture, a transaction consists of multiple local transa -The main advantage of a microservices architecture is loose coupling. Each microservice’s persistent data must be kept private and accessible only through a microservice's API. Changes to the data schema must be carefully evaluated if your microservices share the same database. +The main advantage of a microservices architecture is loose coupling. Each microservice's persistent data must be kept private and accessible only through a microservice's API. Changes to the data schema must be carefully evaluated if your microservices share the same database. @@ -37 +35 @@ The main advantage of a microservices architecture is loose coupling. Each micro -## How can I keep a microservice’s persistent data private if they all share a single database? +## How can I keep a microservice's persistent data private if they all share a single database?