AWS re:Invent 2023 - Data modeling core concepts for Amazon DynamoDB (DAT329)

Поделиться
HTML-код
  • Опубликовано: 21 дек 2024

Комментарии • 14

  • @allanbengco670
    @allanbengco670 Год назад +4

    One of the feature that I most liked about DynamoDB (with GraphQL), is the field level authorization. This feature adds a layer of security in the apps I develop, and implementing "Delete My Data" to comply to GDPR requirements, has become much easier to implement. Thank you DynamoDB!

  • @kxhakol
    @kxhakol 26 дней назад

    Such a great presentation, very insightful!

  • @Anandabganesh0
    @Anandabganesh0 Год назад +1

    Great features inside DynamoDB!!! I liked the partition key/sort key design, secondary indexes and cost optimization.

  • @uunuu0521
    @uunuu0521 Год назад +1

    I have got some experience in DynamoDB and knew how to design PK, SK, and adding prefixes to them.
    Still I learned 2 very important things. Why you should keep items small. Because of cost optimization. And sparse index is pretty nifty and will use it in my projects. Thank you very much!!

  • @taidg_
    @taidg_ 10 месяцев назад

    Great video, very informative with good examples too

  • @newapples1303
    @newapples1303 2 месяца назад +1

    I just finished watching this video, and it was incredibly insightful. Initially, I tried learning through ChatGPT, but after watching the video, I realized that most of the information I received was incorrect. Please continue to share more content on DynamoDB!

    • @awssupport
      @awssupport 2 месяца назад +1

      Thank you for sharing your feedback. We are so glad to hear you enjoyed our content! ✨ ^RN

  • @mikemccarthy9855
    @mikemccarthy9855 2 месяца назад

    Maybe I'm not understanding sparse index, but if you look at ruclips.net/video/l-Urbf4BaWg/видео.htmlsi=3pfgBJ1tmgh7GWtk&t=3048, the slide shows how OrderId003 no longer has the PaymentDate attribute, but the slide shown at ruclips.net/video/l-Urbf4BaWg/видео.htmlsi=u9686wPoLIItYkwM&t=3051 includes OrderId003 in the sparse index. I think this is mistake? What should in the sparse index is OrderId001 and OrderId002, not OrderId003

    • @awssupport
      @awssupport 2 месяца назад

      Hello Mike. I've reached out to our DynamoDB team for clarification on this. ^MA

    • @awssupport
      @awssupport Месяц назад

      Great catch on spotting that error! 🙌 Our DynamoDB team has looked into this & confirmed that OrderId001 & OrderId002 would be present in the Sparse Index & not OrderId003. ^AK

  • @benjaminsh8576
    @benjaminsh8576 2 месяца назад

    everything was going well, until a guy with mask came up!