AWS prescriptive-guidance documentation change
Summary
Updated table formatting, changed note structure, fixed multiplication symbols, and corrected title casing
Security assessment
Changes are purely cosmetic and structural (formatting tables, note sections, and mathematical symbols). No security-related content was added, modified, or referenced. The security requirements table remains unchanged.
Diff
diff --git a/prescriptive-guidance/latest/dynamodb-data-modeling/template-tech-req.md b/prescriptive-guidance/latest/dynamodb-data-modeling/template-tech-req.md index f36e335ac..d838048a1 100644 --- a//prescriptive-guidance/latest/dynamodb-data-modeling/template-tech-req.md +++ b//prescriptive-guidance/latest/dynamodb-data-modeling/template-tech-req.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Modeling data with Amazon DynamoDB](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Modeling data with Amazon DynamoDB](introduction.html) @@ -11 +11 @@ Provide information about data ingestion types: -**Data ingestion type** | **Y/N** | **Description** | **Frequency** +Data ingestion type| Y/N| Description| Frequency @@ -23 +23 @@ Provide information about data consumption types: -**Data consumption type** | **Y/N** | **Description** | **Frequency** +Data consumption type| Y/N| Description| Frequency @@ -37 +37 @@ Provide data volume estimates: -**Entity name** | **Estimated # of records** | **Record size** | **Data volume** +Entity name| Estimated # of records| Record size| Data volume @@ -58 +58 @@ Specify write throughput requirements: -**Entity name** | **Writes/day** | **Hours/day** | **Writes/second** +Entity name| Writes/day| Hours/day| Writes/second @@ -64 +64 @@ _Game User Mapping_ | _1,800,000,000_ | _18_ | _~ 27.777_ -###### Notes +###### Note @@ -67,0 +68,2 @@ _Game User Mapping_ | _1,800,000,000_ | _18_ | _~ 27.777_ +###### Note + @@ -70 +72,3 @@ _Game User Mapping_ | _1,800,000,000_ | _18_ | _~ 27.777_ -**Game User Mapping write operations:** 100,000 games/day for each game with 50 players. The average game duration is 30 minutes, and the gamer position is updated every 5 seconds. We estimate an average of 360 updates per gamer, so the total is 100,000 * 50 * 360 = 1,800,000,000 write operations. +###### Note + +**Game User Mapping write operations:** 100,000 games/day for each game with 50 players. The average game duration is 30 minutes, and the gamer position is updated every 5 seconds. We estimate an average of 360 updates per gamer, so the total is 100,000 × 50 × 360 = 1,800,000,000 write operations. @@ -74 +78 @@ Specify read throughput requirements: -**Entity name** | **Reads / day** | **Hours / day** | **Reads/sec** +Entity name| Reads / day| Hours / day| Reads/sec @@ -80 +84,3 @@ _Game User Mapping_ | _1,800,000,000_ | _18_ | _~ 27.777_ -###### Notes +###### Note + +**Game Player read operations:** 20 percent of users start games, so 1 MM × 0.2 = 200,000. @@ -82 +88 @@ _Game User Mapping_ | _1,800,000,000_ | _18_ | _~ 27.777_ -**Game Player read operations:** 20 percent of users start games, so 1 MM * 0.2 = 200,000. +###### Note @@ -84 +90,3 @@ _Game User Mapping_ | _1,800,000,000_ | _18_ | _~ 27.777_ -**Game Instance read operations:** 100,000 games/day. For each game we have at least 1 read operation per player, and 50 players per game, so the total is 5,000,000 read operations. +**Game Instance read operations** : 100,000 games/day. For each game we have at least 1 read operation per player, and 50 players per game, so the total is 5,000,000 read operations. + +###### Note @@ -86 +94 @@ _Game User Mapping_ | _1,800,000,000_ | _18_ | _~ 27.777_ -**Game User Mapping read operations:** 100,000 games/day for 50 players. The average game duration is 30 minutes, and the gamer position is updated every 5 seconds. We estimate an average of 360 updates per gamer, and each update requires a read operation, so the total is 100,000 * 50 * 360 = 1,800,000,000 read operations. +**Game User Mapping read operations** : 100,000 games/day for 50 players. The average game duration is 30 minutes, and the gamer position is updated every 5 seconds. We estimate an average of 360 updates per gamer, and each update requires a read operation, so the total is 100,000 × 50 × 360 = 1,800,000,000 read operations. @@ -90 +98 @@ Specify data access latency requirements: -**Operation** | **99 percentiles** | **Maximum latency** +Operation| 99 percentiles| Maximum latency @@ -97 +105 @@ Specify data availability requirements: -**Requirement** | **Y/N** | **Metric** | **Notes** +Requirement| Y/N| Metric| Notes @@ -108 +116 @@ Specify security requirements: -**Requirement** | **Y/N** | **Notes** +Requirement| Y/N| Notes @@ -124 +132 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Business-requirements assessment template +Business requirements assessment template