Let's quickly summarize what we just learned. DynamoDB is a fast, simple way to reliably store and access large amounts of data. Dynamo may not be a good choice if you have several tables that require relationship between records. That's a job for Amazon RDS. Consider the import from S3 feature when creating a new table, since it will save you a lot of time by combining several steps into a single data import job. 

If you need to write to DynamoDB from code, consider the AWS SDK and documentations since they probably have a library with sample code in your programming language of choice. When looking for data in your table, a query is always going to be more efficient than a scan. So, when possible, use a query. Provision your table with average or minimal capacity based on estimates. Your application's growth and behavior will tell you exactly how much provision capacity to use. And lastly, plan your DynamoDB table long before deploying it. This will help you determine capacity, partition keys, sort keys, and whether DynamoDB is a good fit for this particular use case. That's it for now. I hope this was helpful to you. And if you have any questions feel free to reach out. My name is Carlos, and I will talk to you in the next one.