AWS prescriptive-guidance documentation change
Summary
Updated URL paths by adding double slashes in multiple documentation links
Security assessment
The changes are purely URL formatting corrections (adding double slashes) without any security-related context or modifications to security features. No evidence of addressing vulnerabilities or security improvements.
Diff
diff --git a/prescriptive-guidance/latest/modernization-data-persistence/welcome.md b/prescriptive-guidance/latest/modernization-data-persistence/welcome.md index 488ac1167..a1504af46 100644 --- a//prescriptive-guidance/latest/modernization-data-persistence/welcome.md +++ b//prescriptive-guidance/latest/modernization-data-persistence/welcome.md @@ -17 +17 @@ Application modernization is a gateway to continuous improvement for your organi - * **[Decompose monoliths into microservices](https://docs.aws.amazon.com/prescriptive-guidance/latest/modernization-decomposing-monoliths/welcome.html)** – Use patterns to break down monolithic applications into microservices. + * **[Decompose monoliths into microservices](https://docs.aws.amazon.com//prescriptive-guidance/latest/modernization-decomposing-monoliths/welcome.html)** – Use patterns to break down monolithic applications into microservices. @@ -19 +19 @@ Application modernization is a gateway to continuous improvement for your organi - * **[Integrate microservices](https://docs.aws.amazon.com/prescriptive-guidance/latest/modernization-integrating-microservices/welcome.html)** – Integrate the newly created microservices into a [microservices architecture](https://docs.aws.amazon.com/whitepapers/latest/microservices-on-aws/simple-microservices-architecture-on-aws.html) by using [Amazon Web Services (AWS) serverless services](https://aws.amazon.com/serverless/). + * **[Integrate microservices](https://docs.aws.amazon.com//prescriptive-guidance/latest/modernization-integrating-microservices/welcome.html)** – Integrate the newly created microservices into a [microservices architecture](https://docs.aws.amazon.com//whitepapers/latest/microservices-on-aws/simple-microservices-architecture-on-aws.html) by using [Amazon Web Services (AWS) serverless services](https://aws.amazon.com//serverless/). @@ -21 +21 @@ Application modernization is a gateway to continuous improvement for your organi - * **Enable data persistence for microservices architecture** – Promote [polyglot persistence](https://martinfowler.com/bliki/PolyglotPersistence.html) among your microservices by decentralizing their [data stores](https://docs.aws.amazon.com/whitepapers/latest/microservices-on-aws/data-store.html). + * **Enable data persistence for microservices architecture** – Promote [polyglot persistence](https://martinfowler.com/bliki/PolyglotPersistence.html) among your microservices by decentralizing their [data stores](https://docs.aws.amazon.com//whitepapers/latest/microservices-on-aws/data-store.html). @@ -26 +26 @@ Application modernization is a gateway to continuous improvement for your organi -Although you can use a monolithic application architecture for some use cases, modern application features often don't work in a monolithic architecture. For example, the entire application can't remain available while you upgrade individual components, and you can't scale individual components to resolve bottlenecks or [hotspots](https://docs.aws.amazon.com/kinesisanalytics/latest/dev/app-hotspots-detection.html) (relatively dense regions in your application's data). Monoliths can become large, unmanageable applications, and significant effort and coordination is required among multiple teams to introduce small changes. +Although you can use a monolithic application architecture for some use cases, modern application features often don't work in a monolithic architecture. For example, the entire application can't remain available while you upgrade individual components, and you can't scale individual components to resolve bottlenecks or [hotspots](https://docs.aws.amazon.com//kinesisanalytics/latest/dev/app-hotspots-detection.html) (relatively dense regions in your application's data). Monoliths can become large, unmanageable applications, and significant effort and coordination is required among multiple teams to introduce small changes. @@ -32 +32 @@ Previously, a typical architectural approach was to model all user requirements -By choosing to decentralize your data stores, you promote [polyglot persistence among your microservices](https://docs.aws.amazon.com/whitepapers/latest/modern-application-development-on-aws/polyglot-persistence.html), and identify your data storage technology based on the data access patterns and other requirements of your microservices. Each microservice has its own data store and can be independently scaled with low-impact schema changes, and data is gated through the microservice’s API. Breaking down a monolithic database is not easy, and one of the biggest challenges is structuring your data to achieve the best possible performance. Decentralized polyglot persistence also typically results in eventual data consistency, and other potential challenges that require a thorough evaluation include data synchronization during transactions, transactional integrity, data duplication, and joins and latency. +By choosing to decentralize your data stores, you promote [polyglot persistence among your microservices](https://docs.aws.amazon.com//whitepapers/latest/modern-application-development-on-aws/polyglot-persistence.html), and identify your data storage technology based on the data access patterns and other requirements of your microservices. Each microservice has its own data store and can be independently scaled with low-impact schema changes, and data is gated through the microservice’s API. Breaking down a monolithic database is not easy, and one of the biggest challenges is structuring your data to achieve the best possible performance. Decentralized polyglot persistence also typically results in eventual data consistency, and other potential challenges that require a thorough evaluation include data synchronization during transactions, transactional integrity, data duplication, and joins and latency. @@ -46 +46 @@ This guide is for application owners, business owners, architects, technical lea - * For steps to implement the saga pattern by using AWS Step Functions, see the pattern [Implement the serverless saga pattern by using AWS Step Functions](https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/implement-the-serverless-saga-pattern-by-using-aws-step-functions.html) on the AWS Prescriptive Guidance website. + * For steps to implement the saga pattern by using AWS Step Functions, see the pattern [Implement the serverless saga pattern by using AWS Step Functions](https://docs.aws.amazon.com//prescriptive-guidance/latest/patterns/implement-the-serverless-saga-pattern-by-using-aws-step-functions.html) on the AWS Prescriptive Guidance website. @@ -55 +55 @@ The guide is part of a content series that covers the application modernization - * [Strategy for modernizing applications in the AWS Cloud](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-modernizing-applications/) + * [Strategy for modernizing applications in the AWS Cloud](https://docs.aws.amazon.com//prescriptive-guidance/latest/strategy-modernizing-applications/) @@ -57 +57 @@ The guide is part of a content series that covers the application modernization - * [Phased approach to modernizing applications in the AWS Cloud](https://docs.aws.amazon.com/prescriptive-guidance/latest/modernization-phased-approach/) + * [Phased approach to modernizing applications in the AWS Cloud](https://docs.aws.amazon.com//prescriptive-guidance/latest/modernization-phased-approach/) @@ -59 +59 @@ The guide is part of a content series that covers the application modernization - * [Evaluating modernization readiness for applications in the AWS Cloud](https://docs.aws.amazon.com/prescriptive-guidance/latest/modernization-assessing-applications/welcome.html) + * [Evaluating modernization readiness for applications in the AWS Cloud](https://docs.aws.amazon.com//prescriptive-guidance/latest/modernization-assessing-applications/welcome.html) @@ -61 +61 @@ The guide is part of a content series that covers the application modernization - * [Decomposing monoliths into microservices](https://docs.aws.amazon.com/prescriptive-guidance/latest/modernization-decomposing-monoliths/welcome.html) + * [Decomposing monoliths into microservices](https://docs.aws.amazon.com//prescriptive-guidance/latest/modernization-decomposing-monoliths/welcome.html) @@ -63 +63 @@ The guide is part of a content series that covers the application modernization - * [Integrating microservices by using AWS serverless services](https://docs.aws.amazon.com/prescriptive-guidance/latest/modernization-integrating-microservices/welcome.html) + * [Integrating microservices by using AWS serverless services](https://docs.aws.amazon.com//prescriptive-guidance/latest/modernization-integrating-microservices/welcome.html) @@ -84 +84 @@ You should expect the following six outcomes from promoting data persistence amo - * Build highly scalable and distributed applications by choosing from more than [15 purpose-built database engines on the AWS Cloud](https://aws.amazon.com/products/databases/). + * Build highly scalable and distributed applications by choosing from more than [15 purpose-built database engines on the AWS Cloud](https://aws.amazon.com//products/databases/).