AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb link, changed section title from 'Use queries instead of scans' to 'Run queries instead of scans', fixed anchor link reference, and corrected apostrophe usage.
Security assessment
Changes are editorial/navigational improvements without security implications. The 'queries vs scans' recommendation relates to performance/cost optimization, not security vulnerabilities or features. No security-specific content was added or modified.
Diff
diff --git a/prescriptive-guidance/latest/modernization-rdbms-dynamodb/best-practices.md b/prescriptive-guidance/latest/modernization-rdbms-dynamodb/best-practices.md index 1c1983d9e..20423836f 100644 --- a//prescriptive-guidance/latest/modernization-rdbms-dynamodb/best-practices.md +++ b//prescriptive-guidance/latest/modernization-rdbms-dynamodb/best-practices.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Modernizing your application by migrating from an RDBMS to Amazon DynamoDB](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Modernizing your application by migrating from an RDBMS to Amazon DynamoDB](introduction.html) @@ -7 +7 @@ -Use the object persistence access patternChoose the correct capacity provisioning modeUse cachingUse queries instead of scansValidate data integrity +Use the object persistence access patternChoose the correct capacity provisioning modeUse cachingRun queries instead of scansValidate data integrity @@ -15 +15 @@ This section summarizes recommendations in addition to the best practices discus -As discussed earlier in this guide, Amazon DynamoDB provides three access patterns. The [object persistence interface](./access-patterns.html#object-persistence-interface) provides clean and easy-to-maintain code. Unless you have to customize or transform model property values during read/write operations, we recommend that you use the object persistence interface. +As discussed earlier in this guide, DynamoDB provides three access patterns. The [object persistence interface](./access-patterns.html#object-persistence-interface) provides clean and easy-to-maintain code. Unless you have to customize or transform model property values during read/write operations, we recommend that you use the object persistence interface. @@ -19 +19 @@ As discussed earlier in this guide, Amazon DynamoDB provides three access patter -On-demand capacity provisioning automatically scales read and write operations as your workloads ramp up and down. We recommend that you use this mode if your workload is unpredictable. The cost is usually higher than provisioned capacity mode, and is charged on a pay-as-you-use basis. We recommend that you use provisioned capacity mode when your workload is predictable and you can forecast your capacity requirements. For more information, see the [Pricing models](./overview.html#features-pricing) section earlier in this guide. +On-demand capacity provisioning automatically scales read and write operations as your workloads ramp up and down. We recommend that you use this mode if your workload is unpredictable. The cost is usually higher than provisioned capacity mode, and is charged on a pay-as-you-use basis. We recommend that you use provisioned capacity mode when your workload is predictable and you can forecast your capacity requirements. For more information, see the [Pricing models](./overview.html#features) section earlier in this guide. @@ -25 +25 @@ We recommend that you use caching when working with DynamoDB to reduce the cost -## Use queries instead of scans +## Run queries instead of scans @@ -31 +31 @@ Avoid DynamoDB scans as much as possible. A DynamoDB query is more efficient and -DynamoDB is a NoSQL database, so it doesn’t maintain relationship data or include data integrity constraints. It requires each item to have a unique combination of a primary key and sort key only. To ensure data integrity between related items in DynamoDB table, we recommend that you perform strict validations in the application or business layer of your system. +DynamoDB is a NoSQL database, so it doesn't maintain relationship data or include data integrity constraints. It requires each item to have a unique combination of a primary key and sort key only. To ensure data integrity between related items in DynamoDB table, we recommend that you perform strict validations in the application or business layer of your system. @@ -39 +39 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Converters +Sample application