AWS prescriptive-guidance documentation change
Summary
Updated navigation links, removed hyperlink from 'modernize', adjusted hyperlink placement for 'event-driven', and added comma after 'Bulkheads' for grammatical correctness
Security assessment
Changes involve link updates, formatting adjustments, and punctuation fixes without introducing new security content or addressing vulnerabilities. References to security improvements remain unchanged and are not the focus of these edits.
Diff
diff --git a/prescriptive-guidance/latest/aws-caf-platform-perspective/modern-apps.md b/prescriptive-guidance/latest/aws-caf-platform-perspective/modern-apps.md index a7d49f6dc..7342edb00 100644 --- a//prescriptive-guidance/latest/aws-caf-platform-perspective/modern-apps.md +++ b//prescriptive-guidance/latest/aws-caf-platform-perspective/modern-apps.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[AWS Cloud Adoption Framework: Platform perspective](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[AWS Cloud Adoption Framework: Platform perspective](introduction.html) @@ -23 +23 @@ Building well-architected, cloud-native applications requires a deep understandi -Start by investigating containers, serverless technologies, and other approaches that enable the development of [microservices](https://aws.amazon.com/microservices/), which enhance resource efficiency, help improve security, and minimize infrastructure expenses. Choose to [modernize](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-modernizing-applications/welcome.html) your existing differentiating and enterprise applications to improve efficiency and maximize the value of your existing investments. Contemplate [replatforming](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-replatforming-cots-applications/welcome.html) (transitioning your self-managed containers, databases, or message brokers to managed cloud services) and [refactoring](https://docs.aws.amazon.com/prescriptive-guidance/latest/modernization-decomposing-monoliths/welcome.html) (redeveloping your applications to adopt cloud-native architectures) based on value-led decision-making. +Start by investigating containers, serverless technologies, and other approaches that enable the development of [microservices](https://aws.amazon.com/microservices/), which enhance resource efficiency, help improve security, and minimize infrastructure expenses. Choose to modernize your existing differentiating and enterprise applications to improve efficiency and maximize the value of your existing investments. Contemplate [replatforming](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-replatforming-cots-applications/welcome.html) (transitioning your self-managed containers, databases, or message brokers to managed cloud services) and [refactoring](https://docs.aws.amazon.com/prescriptive-guidance/latest/modernization-decomposing-monoliths/welcome.html) (redeveloping your applications to adopt cloud-native architectures) based on value-led decision-making. @@ -25 +25 @@ Start by investigating containers, serverless technologies, and other approaches -When you update your existing cloud-based application, a successful approach involves using the [strangler fig pattern](https://aws.amazon.com/blogs/architecture/seamlessly-migrate-on-premises-legacy-workloads-using-a-strangler-pattern/) to progressively decompose your architecture into microservices. This procedure aids in adopting a contemporary application methodology, so you can realize the inherent benefits and demonstrate its value to the larger organization. Consider constructing your applications as distinct microservices that harness [event-driven architectures](https://aws.amazon.com/event-driven-architecture/) where applicable. Ensure that your architecture takes into account unchangeable [service quotas](https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/manage-service-quotas-and-constraints.html) and physical resources to avoid affecting workload performance or reliability. +When you update your existing cloud-based application, a successful approach involves using the [strangler fig pattern](https://aws.amazon.com/blogs/architecture/seamlessly-migrate-on-premises-legacy-workloads-using-a-strangler-pattern/) to progressively decompose your architecture into microservices. This procedure aids in adopting a contemporary application methodology, so you can realize the inherent benefits and demonstrate its value to the larger organization. Consider constructing your applications as distinct microservices that harness [event-driven](https://aws.amazon.com/event-driven-architecture/) architectures where applicable. Ensure that your architecture takes into account unchangeable [service quotas](https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/manage-service-quotas-and-constraints.html) and physical resources to avoid affecting workload performance or reliability. @@ -71 +71 @@ Microservices offer a highly scalable, resilient, and agile application architec -[Circuit breakers](https://docs.aws.amazon.com/prescriptive-guidance/latest/cloud-design-patterns/circuit-breaker.html) act as a safety mechanism that prevents cascading failures by temporarily halting or shifting communications from an unhealthy service, so it can recover. [Bulkheads](https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/rel_fault_isolation_use_bulkhead.html) isolate resources and limit the scope of impact of potential failures. Together, these patterns create a robust architecture that withstands unforeseen disruptions and maintains optimal performance. +[Circuit breakers](https://docs.aws.amazon.com/prescriptive-guidance/latest/cloud-design-patterns/circuit-breaker.html) act as a safety mechanism that prevents cascading failures by temporarily halting or shifting communications from an unhealthy service, so it can recover. [Bulkheads](https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/rel_fault_isolation_use_bulkhead.html), isolate resources and limit the scope of impact of potential failures. Together, these patterns create a robust architecture that withstands unforeseen disruptions and maintains optimal performance.