AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb navigation links, fixed contractions, and removed '(ASMX)' from a heading.
Security assessment
Changes are purely editorial - updating links, fixing grammar, and minor text formatting. No security-related content was added or modified.
Diff
diff --git a/prescriptive-guidance/latest/modernization-aspnet-web-services/considerations.md b/prescriptive-guidance/latest/modernization-aspnet-web-services/considerations.md index f11896871..3b9d30213 100644 --- a//prescriptive-guidance/latest/modernization-aspnet-web-services/considerations.md +++ b//prescriptive-guidance/latest/modernization-aspnet-web-services/considerations.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Modernizing legacy Microsoft ASP.NET (ASMX) web services incrementally by using containers and Amazon API Gateway](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Modernizing ASP.NET (ASMX) web services incrementally by using containers and Amazon API Gateway](introduction.html) @@ -11 +11 @@ Authentication and authorizationDomain-driven designInterim states and target st -So far, we’ve discussed using API Gateway and Windows containers to modernize your legacy ASP.NET web services on AWS. Here are some other considerations to take into account: +So far, we've discussed using API Gateway and Windows containers to modernize your legacy ASP.NET web services on AWS. Here are some other considerations to take into account: @@ -34 +34 @@ When breaking a monolith into individual services, domain-driven design (DDD) is -When you're modernizing more than a few ASP.NET web services on AWS, it is a good practice to first define what your target state architecture will be after all services are modernized. However, the target state architecture isn’t necessarily the end state or the final state, because business contexts change often and the system target state should be updated as needed to stay aligned with the business goals. When you’ve defined the target state, you can work backward from there to define interim-state architectures that incrementally fulfill the target state vision. You can think of these interim-state architectures as the progression of the strangler fig vine up the tree as it encounters and engulfs major portions of the host tree. Interim-state architectures often introduce temporary or overlapping constructs that will not be part of the end-state architecture in order to facilitate the evolution to the target state. The modernization of the SOAP-based ASP.NET web service provides an example of this: A Windows-based container is introduced temporarily to bridge the gap between calling systems that are dependent on the legacy service until they can be upgraded to the new REST API. +When you're modernizing more than a few ASP.NET web services on AWS, it is a good practice to first define what your target state architecture will be after all services are modernized. However, the target state architecture isn't necessarily the end state or the final state, because business contexts change often and the system target state should be updated as needed to stay aligned with the business goals. When you've defined the target state, you can work backward from there to define interim-state architectures that incrementally fulfill the target state vision. You can think of these interim-state architectures as the progression of the strangler fig vine up the tree as it encounters and engulfs major portions of the host tree. Interim-state architectures often introduce temporary or overlapping constructs that will not be part of the end-state architecture in order to facilitate the evolution to the target state. The modernization of the SOAP-based ASP.NET web service provides an example of this: A Windows-based container is introduced temporarily to bridge the gap between calling systems that are dependent on the legacy service until they can be upgraded to the new REST API. @@ -42 +42 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -SOAP-based ASP.NET web services (ASMX) +SOAP-based ASP.NET web services