Technical requirements assessment template - AWS Prescriptive Guidance

Technical requirements assessment template

Provide information about data ingestion types:


    Providing data ingestion information

Provide information about data consumption types:


    Providing data consumption information

Provide data volume estimates:


    Providing data volume estimates

Note

The period for data retention is 60 days. After 60 days, data must be stored in Amazon S3 for analytics, by using DynamoDB Time to Live (TTL) to automatically move data out of DynamoDB to Amazon S3.

Answer these questions about time patterns:

  • What time frame is the application available to the user (for example, 24/7 or 9 AM to 5 PM on weekdays)?

  • Is there a peak in usage during the day? How many hours? What is the percentage of application usage?

Specify write throughput requirements:


    Specifying write throughput requirements

Notes

Game Player write operations: 1 percent of users update their profiles every day, so we expect 10,000 updates for 1,000,000 users.

Game Instance write operations: 100,000 games/day. For each game we have at least 3 write operations—at creation, start, and end—so the total is 300,000 write operations.

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.

Specify read throughput requirements:


    Specifying read throughput requirements

Notes

Game Player read operations: 20 percent of users start games, so 1 MM * 0.2 = 200,000.

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 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.

Specify data access latency requirements:


    Specifying data access latency requirements

Specify data availability requirements:


    Specifying data availability requirements

Specify security requirements:


    Specifying security requirements