HackerTube 中文?

AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401)

Amazon Web ServicesYouTube ↗

Further reading 1

Can one record tell you both now and then? →Two reads disagree. First ask which moment each value describes, then who can change it. Keeping history and coordinating writes solve different problems.This video helps answer · What did the record say at the time?

Caption notes

Start DynamoDB modeling with the access patterns. Composite keys and indexes can answer predictable queries without joins, but partitioning and lifecycle choices matter.

Original passages · 6
I need to know exactly what the application is doing
AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401) · ▶ 27:59–28:08
the more that I tune that data to the access pattern the more tightly coupled to that service I am
AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401) · ▶ 29:44–29:52
the filter condition applies after the read so
AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401) · ▶ 36:14–36:20
the metric is calculated now it can be read a million times
AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401) · ▶ 33:52–33:59
understand every access pattern I need to know
AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401) · ▶ 27:59–28:05
we want single queries to deliver multiple entities
AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401) · ▶ 52:26–52:33

Hacker News comments

View original on HN ↗