AWS re:Invent 2019: [REPEAT 1] Amazon DynamoDB deep dive: Advanced design patterns (DAT403-R1)

I wrote a piece that touches a bit on the why: [LINK] But in a nutshell: availability and scalability. Yes you can achieve this with relational DBs, but it will be quite complex, while No-SQL gives it by design. All while ensuring all the goodness of relational data modeling, consistency and queries. The only requirement is a good table design: [VIDEO]

Interesting question. No-SQL doesn't mean non-relational. DynamoDB is a relational database. It's up to you on how you design the table to accommodate your relations. This is a great presentation about this: [VIDEO]

Rick has had the most-watched re:Invent talk the last three years. Here are the links for each: - 2019: [VIDEO] - 2018: [LINK] - 2017: [LINK] Additional DynamoDB links here: [LINK]

You never heard of Rick Houlihan? He is the 90% of DynamoDB Evangelism... At the same time you are able to this internal lookups? Do you work with DynamoDB? AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401) [LINK] AWS re:Invent 2019: [REPEAT 1] Amazon DynamoDB deep dive: Advanced design patterns (DAT403-R1) [VIDEO] AWS re:Invent 2020: Amazon DynamoDB advanced design patterns – Part 1 [LINK] AWS re:Invent 2020: Amazon DynamoDB advanced design patterns – Part 2 [LINK] AWS re:Invent 2021 - DynamoDB deep dive: Advanced design patterns [LINK] Amazon DynamoDB | Office Hours with Rick Houlihan: Breaking down the design process for NoSQL applications [LINK]