What Did I Learn -
I learned, or re-learned quite a bit about Indexes for DynamoDB. For example, Local Secondary Indexes have to be generated when you create your table, unlike the Global secondary index, local uses same partition key as your table and global uses a different one, and how they both utilize different sort key, which goes with the whole concept of "Secondary Index" I think. I also learned within a query you can reverse the order results by setting the ScanIndexForward parameter = false(It is also helpful to know this is for a query). In Postgres I would generally set to Asc or Desc when specifying Order by, so this was helpful to find out. Also that a Scan does not search a database, but grabs the entire database, and you have the option to filter information out based on what you need. Another helpful tip is that queries find info in a table only using primary keys. I also learned the calculations for Provisioned throughput | 1 Write Capacity Unit = 1KB WPS (Write per second), 1 Read Capacity Unit = 1 x4KB Strongly consistent Read OR 2x4KB Eventually Consistent reads per second.
What Did I Do -
We just kept it simple on this one, we went to DynamoDB, we were prompted to make a table, enter our table name, we just used NewTable and for our primary key we just used primary-key as the string. From here we use the create item tab to create new item key value pairs, such as Field as item value as socks, price:5, etc with the + append button, note that + insert will add above the line you are currently on, while the + append adds below it.
For Tomorrow -
Tomorrow, or rather today it is all about AWS KMS
Top comments (0)