Skip to content
0:00 / 0:00

#dynamodb#aws#single-tabledesign

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

AWS Events

185K subscribers • 7 videos on Hallway

YouTube
  • Recommended by 1 person: 1 on Hacker News.
  • Presented by Rick Houlihan
  • Made by the vendor. The company whose product it covers made or sponsored it.
  • May be out of date. Uploaded 6 years ago, in an area where tools change fast.

Advanced. Deep dive for people who know the field.

114K views6 years ago1 recommendation

Databases and dataCloud and DevOpsNoSQL and document databasesDatabase internalsSoftware architecture

Rick Houlihan presents advanced design patterns and data modeling strategies for building highly scalable solutions with Amazon DynamoDB.

This technical session is for advanced users of Amazon DynamoDB. The patterns and data models discussed in this presentation summarize a collection of implementations and best practices used by large customers—including Amazon retail businesses—to deliver highly scalable solutions for a wide variety of business problems. We delve into strategies for global secondary index sharding and index overloading, scalable graph processing with materialized queries, relational modeling with composite keys, executing transactional workflows on DynamoDB, and more.

Why it's here

1 person recommends this

What people say. Highly recommended as the definitive guide to advanced DynamoDB data modeling and single-table design.

andriosron Hacker News • Recommends

On “Show HN: An open-source financial ledger API written in Clojure”

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: link to this video

andriosron Hacker News • Recommends

On “Show HN: An open-source financial ledger API written in Clojure”

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: link to this video

abd12on Hacker News • Mentions

On “Rules for Data Modeling with DynamoDB”

Rick has had the most-watched re:Invent talk the last three years. Here are the links for each: - 2019: link to this video - 2018: link - 2017: link Additional DynamoDB links here: link

belteron Hacker News • Mentions

On “DynamoDB 10 years later”

…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) link to this 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…

u/too_much_exceptionsin r/softwarearchitecture • Mentions

On “What distributed data store to learn the architecture concepts?”

Regarding DynamoDB this one is pretty good link to this video Enjoy ;)