❝HN 片单

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

Amazon Web Services · 6 位 HN 用户推荐 · 2019–2022

  1. While the move seems to be towards NewSQL databases (Spanner/CockroachDB), the answer to relations in NoSQL is to model the data differently. This can generally resolve a lot of the problems inherent in the need for relations. This might not be useful advice for everyone, but I can highly recommend this [link] video on DynamoDB data modelling: [link]
    — dalailambda, 2019
  2. If you go single table you can use filtered indexes if your database supports it to speed up queries instead of having to do a row by row search with a where clause. Personally this seems like a job for DynamoDB but that’s a whole beast unto itself. You must know the queries you will do to the database before hand as that guides how you craft it. There’s an amazing talk at reinvent that is given
    — gigatexal, 2019
  3. AWS re:invent 2018 talks: [link]
    — tmsh, 2019
  4. I've seen this done for new projects, and it works really well. If your data access patterns are truly relational (varied lookup paths) then it is probably not the right tool, but many apps can be modeled in a way that DDB handles well. Highly recommended viewing: [link] this talk explains how relational data can be efficiently modeled for key-value stores.
    — kbanman, 2020
  5. Check out this video from AWS's Principal Dynamodb expert that touches on comparisons against relation db's: [link]
    — holler, 2020
  6. This is the video I recommend to others when working with dynamodb. The video is by Rick Houlihan about dynamodb modeling. In my experience most developers that complain about dynamodb don't fully understand it. [link]
    — sass_muffin, 2022

← HN 片单